test

Sun N1 System Manager 1.3 Release Notes

N1 System Manager Installation and Configuration Issues

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

N1 System Manager Can Fail to Install on Sun Fire X4100 and Sun Fire X4200 Servers (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 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 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.

    SUNWspsc1

    SUNWspsms

    SUNWspsml 


    # pkgrm SUNWspsc1.\*
# pkgrm SUNWspsms.\*
# pkgrm SUNWspscl.\*

    There may be more than one instance of the SPS packages 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 removed by 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.

Restoring N1 System Manager Database on a Solaris x86 Management Server Fails on First Try (6390592)

Restoring the N1 System Manager database using the n1smrestore.sh command on a Solaris x86 management server fails and produces the following type of errors:


DBD::Pg::st execute failed: ERROR: Relation "as_system_config" does not exist at 
     /opt/SUNWscs/lib/perl5/SCSDB.pm line 508.
INFO   : Could not load config object
INFO   : Using defaults
DBD::Pg::st execute failed: ERROR: Relation "as_system_config" does not exist at 
     /opt/SUNWscs/lib/perl5/SCSDB.pm line 508.
INFO   : Could not load config object
INFO   : Using defaults
DBD::Pg::st execute failed: ERROR: Relation "as_ris" does not exist at 
     /opt/SUNWscs/lib/perl5/SCSDB.pm line 508.
No RIS servers defined

Workaround: Run the n1smrestore.sh command a second time.

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

Switching Between ISC DHCP and Solaris DHCP Does Not Work on a Solaris Management Server (6403939)

If you install and configure ISC DHCP and then change the DHCP server to Solaris DHCP, OS deployments will fail.

Workaround: You need to run the n1smconfig script and select the provisioning interface again by replying yes to the following question:


Do you wish to modify the network interface or DHCP range used for the
Provisioning Network? ([n]/y) y

Switching DHCP Service Using n1smconfig Removes DHCP Subnet Configurations (6406109)

If you create new DHCP subnets using the create dhcpconfig command and then use n1smconfig to switch to a different DHCP service, your customized DHCP subnet configurations are removed.

Workaround: Use the following commands instead of n1smconfig to change your DHCP service: