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:

1. 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"

2. 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

3. 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.

4. Delete the service provisioning directory and files.

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

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

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

1. Stop the server and agent.

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

2. Delete the service provisioning directory and files.

   # cd / # rm -rf /opt/sun/N1_Grid_Service_Provisioning_System_5.1 # rm -rf /opt/sun/N1_Grid_Service_Provisioning_System # rm -rf /opt/sun/N1_Service_Provisioning_System # rm -rf /opt/sun/N1_Service_Provisioning_System_5.2 # rm /n1gc-setup/sps/state # rm /n1gc-setup/state/0installSPS.pl.state

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