Sun N1 System Manager 1.3.2 Release Notes

Installation and Configuration Issues

This section describes known N1 System Manager installation and configuration issues.

Check the localization settings of the system prior to installation. The settings need to be consistent and not mixed.
On a Sun Blade X8400 system using the Solaris 10 3/05 Operating System (OS), you must choose ISC DHCP if you are configuring N1 System Manager.

N1 System Manager Does Not Automatically Restart After Backup and Restore (6444305)

N1 System Manager on a Solaris SPARC or x86 management server does not automatically restart after backup and restore. You might get the following error message:

Lost connection to command line service.

Workaround: Restart N1 System Manager manually by typing the following command:

# svcadm enable n1sm

Occasionally Unable to Run `n1sh` Shell After Installation and Configuration (6443655)

Workaround: SSL certificates might be corrupted. Regenerate the security keys by issuing the following commands:

# /opt/sun/cacao/bin/cacaoadm stop

# /opt/sun/cacao/bin/cacaoadm create-keys --force

# /opt/sun/cacao/bin/cacaoadm start

For detailed steps, refer to Regenerating Common Agent Container Security Keys in Sun N1 System Manager 1.3.1 Troubleshooting Guide.

Java Web Console Is Removed After N1 System Manager Uninstall (6433383)

When N1 System Manager is installed and uninstalled, the Java^TM Web Console is removed from the system. The packages of Java Web Console are not available in the system.

Workaround: Before uninstalling N1 System Manager, run the rm /n1gc-setup/installer/jobs/3installLockhart.pl script.

Stopping N1 System Manager Stops the Java Web Console (6432305)

Workaround: Restart the Java Web Console by using /usr/sbin/smcwebserver start.

When Installation Is Cancelled, User Interface Components Are Not Installed (6430787)

If you cancel the N1 System Manager installation process by pressing Control-C, the user interface components are not installed.

Workaround: Manually uninstall the user interface components using /usr/share/webconsole/bin/setup -u -f. Run the installer again.

N1 System Manager Database Does Not Start After Solaris x86 Management Server Reboots (6398263)

In some rare instances, the N1 System Manager database does not start after a Solaris x86 management server boot. A typical error message is as follows:

DBI connect('dbname=mgmt;port=5434','mgmt',...) failed: 
could not connect to server: No such 
file or directory at /opt/SUNWscs/lib/perl5/SCSDB.pm

Workaround: Restart the N1 System Manager database manually on the management server:

# svcadm clear scs-db
# svcadm restart scs-db

N1 System Manager Can Fail to Install (6284696)

If the N1 System Manager installation process is interrupted and restarted, the N1 System Manager installation can fail in Step 5, “Install OS provisioning components.” If this issue occurs, a subsequent uninstall and reinstall of the N1 System Manager will fail.

The installation log file /var/tmp/installer.log.latest shows the following message after initial installation failure:

Installing Master Server ...
Error! Missing file (looked for /opt/SUNWn1sps 
  /N1_Grid_Service_Provisioning_System_5.2
  /server/postgres/postgresql.conf.in)!
print() on closed filehandle GEN0 at 
  /usr/perl5/5.8.4/lib/i86pc-solaris-64int/IO/Handle.pm line 399.
SPS install failed with exit status: 256
-----------------------------

      2k. Which port should Postgres listen on?
          (default: 5434) [1024-65535] spawn id(3) is not a tty. Not changing mode 
  at /usr/perl5/site_perl/5.8.4/Expect.pm line 375.
admin
admin
admin

      ** Invalid Input.  Enter a numeric value for the port number.

      2k. Which port should Postgres listen on?
          (default: 5434) [1024-65535] spawn id(3) is not a tty. Not changing mode 
  at /usr/perl5/site_perl/5.8.4/Expect.pm line 375.
admin
admin
admin

      ** Invalid Input.  Enter a numeric value for the port number.

      2k. Which port should Postgres listen on?
          (default: 5434) [1024-65535

The installation log shows the following message after uninstall and reinstall of the N1 System Manager software:

Error!  Failed to initialize the database (exit value was 1).
Exiting..
print() on closed filehandle GEN0 at /usr/lib/perl5/5.8.0
   /i386-linux-thread-multi/IO/Handle.pm line 395.
SPS install failed with exit status: 256

Workaround: Perform the workaround procedure below that is applicable to the operating system installed on your management server. Depending on how the installation error occurred, some of the workaround steps might not complete successfully. If a workaround step does not complete successfully, go to the next step.

Solaris based Sun Fire X4100 or Sun Fire X4200 management server:

Stop the server and agent.

# su - n1gsps -c "/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/
server/bin/cr_server stop"
# su - n1gsps -c "/opt/SUNWn1sps/N1_Service_Provisioning_System/
agent/bin/cr_agent stop"

Uninstall service provisioning manually.

# /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/cli/bin/cr_uninstall_cli.sh
# /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server/bin/cr_uninstall_ms.sh

Remove the following packages.
# pkgrm SUNWspsc1.\* # pkgrm SUNWspsms.\* # pkgrm SUNWspscl.\*
More than one instance of the SPS packages might be installed. The text string .\* specifies that all instances of the package will be removed.

Type y in response to prompts asking “Do you want to remove this package? [y,n,?,q]”. If the message pkgrm: ERROR: no package associated with SUNWspscl appears, that package has already been removed in Step 2. Continue removing packages.

Delete the service provisioning directory and files.

# cd /
# rm  -rf  /opt/SUNWn1sps/
# rm /n1gc-setup/sps/state
# rm /n1gc-setup/state/0installSPS.pl.state

Reboot the management server and then install the N1 System Manager software.

Linux based Sun Fire X4100 or Sun Fire X4200 management server: