test

Sun N1 Service Provisioning System 6.0 Release Notes

Installation Issues

This section describes known issues with installation.

Solaris: Master Server Installation in Non-Global Zone Fails (6423893)

If you try to install the Sun N1 Service Provisioning System master server software in a non-global zone on a Solaris 10 system, the installation fails. The following error is displayed.


 Checking your Shared Memory and Semaphore configuration.
                Checking for module 'shmsys'
                Module 'shmsys' is not loaded.  Attempting to load the module.
Insufficient privileges to load a module
        Load module 'shmsys' and then restart the N1 SPS Master Server Installer 
       (try this: modload /kernel/sys/shmsys)
                Checking for module 'semsys'
                Module 'semsys' is not loaded.  Attempting to load the module.
Insufficient privileges to load a module
        Load module 'semsys' and then restart the N1 SPS Master Server Installer
        (try this: modload /kernel/sys/semsys)

Workaround: Manually load the shmsys and semsys modules, then retry the installation.


# modload /kernel/sys/shmsys
# modload /kernel/sys/semsys

Solaris x86: Secure Shell Session Does Not Terminate After Remote Installation of Remote Agent (6551914)

If you use the cr_ra_remote command to remotely install a remote agent over a secure shell connection (SSH) from a master server that is running the Solaris 9 OS, the SSH session does not terminate correctly.

Workaround: Apply patch ID 114357-05 or newer to the master server before you install the remote agent.

Solaris: Installation Scripts Fail in Bourne Shell (6568718)

If you run the Sun N1 Service Provisioning System scripts in a Bourne shell, the installation fails. An error message similar to the following is displayed.


cr_cli_solaris_sparc_pkg_6.0.sh: /: cannot execute
Usage: grep -hblcnsviw pattern file . . .

Workaround: Follow these steps.

  1. Assign execution permissions to the installer script.


    # chmod +x installer-script

    Where installer-script refers to the following scripts.

    • cr_ms_solaris_sparc_pkg_6.0.sh

    • cr_ms_solaris_x86__pkg_6.0.sh

    • cr_cli_solaris_sparc_pkg_6.0.sh

    • cr_cli_solaris_x86_pkg_6.0.sh

    • cr_ld_solaris_sparc_6.0.sh

    • cr_ld_solaris_x86_6.0.sh

    • cr_ra_solaris_sparc_6.0.sh

    • cr_ra_solaris_x86_6.0.sh

  2. Launch the installer.

    • For the master server, type the appropriate command.

      • For SPARC systems:


        # ./ksh cr_ms_solaris_sparc_pkg_6.0.sh

      • For x86 systems:


        # ./ksh cr_ms_solaris_x86_pkg_6.0.sh

    • For the CLI client, type the appropriate command.

      • For SPARC systems:


        # ksh cr_cli_solaris_sparc_pkg_6.0.sh

      • For x86 systems:


        # ksh cr_cli_solaris_x86_pkg_6.0.sh

    • For the local distributor, type the appropriate command.

      • For SPARC systems:


        # ksh cr_ld_solaris_sparc_6.0.sh

      • For x86 systems:


        # ksh cr_ld_solaris_x86_6.0.sh

    • For the remote agent, type the appropriate command.

      • For SPARC systems:


        # ksh cr_ra_solaris_sparc_6.0.sh

      • For x86 systems:


        # ksh cr_ra_solaris_x86_6.0.sh

N1 SPS Software Does Not Start After Reboot if SSL Connectivity Is Selected During Installation (6575906)

During the Sun N1 Service Provisioning System installation program, if you select an SSL selection, and select to reboot the host system after the installation, the N1 SPS software does not start after the reboot.

The following message is displayed in the /var/svc/log/application-management-spsra:default.log file.


Invalid password. The password has to be greater than 6 characters in length
Please enter the plaintext password for keystore:stty: : No such device or address

This issue occurs on systems that are running the Solaris OS or Linux operating systems.

Workaround: Choose the appropriate workaround.

Cannot Install in Root (/) Directory (6457372)

During the Sun N1 Service Provisioning System installation program, if you specify the root directory (/) as the installation location for Sun N1 Service Provisioning System, the installation fails. This failure occurs on the following platforms.

Workaround: Specify a non-root directory as the installation directory for the Sun N1 Service Provisioning System.

Solaris: PostgreSQL Database Does Not Start After Installation if Shared Memory Is Not Available (6562505)

If, after you install the Sun N1 Service Provisioning System, the system shared memory is not available, the PostgreSQL database does not start successfully. An error message similar to the following is displayed.


FATAL:  could not create shared memory segment: Invalid argument
DETAIL:  Failed system call was shmget(key=9001001, size=427900928, 03600).
HINT:  This error usually means that PostgreSQL's request for a shared memory segment 
exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or 
reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 
427900928 bytes), reduce PostgreSQL's shared_buffers parameter (currently 51200) 
and/or its max_connections parameter (currently 52).
        If the request size is already small, it's possible that it is less than 
your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
        The PostgreSQL documentation contains more information about shared memory 
configuration.
Error! Failed to start the postgres database using pg_ctl!

Workaround: Choose the appropriate workaround.

Solaris x86: Master Server Installation Fails on Systems With Patch 118855-30 (6567294)

If you install the N1 SPS master server on a Solaris 10 x86 system that has patch ID 118855-30 installed, the installation fails. The following error message is displayed.


Checking for required and recommended Solaris 5.10 patches.
        Patch 124631-03 is required for this installation and does not exist on
your system.
        Patch 120273-13 is required for this installation and does not exist on
your system.

Workaround: Add patches 124631-03 and 120273-13 or greater version, then reinstall the N1 SPS software on the master server.

Windows: Resource Check Ins Might Be Rejected (6396403)

Per a recent change in the way resource space is managed, the variable used to configure the Master Server resource repository size has changed in name and function. Therefore, the default configuration files need to be changed.

The new variable, rsrc.minMSRepoVolFreeSpace, specifies the minimum number of bytes of disk space that should remain available before further resource check ins are rejected. If a value is not given to rsrc.minMSRepoVolFreeSpace, the Master Server can use as much disk space as needed, up to the entire disk.

Workaround: On Windows Master Servers, manually delete configuration variable rsrc.maxMSRepoSize and add the new configuration variable rsrc.minMSRepoVolFreeSpace. Both variables pertain to the management of resource disk space on the Master Server.

Windows: Windows 2000 Installation Might Fail When Configuring HTTPS (6398475)

While installing the Sun N1 Service Provisioning System 6.0 Master Server on Windows, the installation fails when selecting the I Am Ready to Specify the HTTPS configuration now option. When choosing this option, the installer prompts for keystore file path and keystore password. The installation might fail by throwing the following error:

Error 1720: There is a problem with this windows installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.

The possible causes for this error are:

Workaround: To prevent an error, verify the following:

As an alternative, you can also select the I will specify the HTTPS configuration after the install option instead of the I am ready to specify the HTTPS configuration now option and perform keystore configuration later.

For more information, see Creating a Keystore File and Keystore Password for HTTPS Connections in Sun N1 Service Provisioning System 6.0 Installation Guide.

Problems Starting the Master Server on Solaris Systems That Do Not Meet Minimum System Configuration Requirements (6395197)

The N1 SPS Master Server uses the PostgreSQL database. PostgreSQL requires a shared memory segment when it is started. If the PostgreSQL's request for a shared memory segment exceeds available memory, then database startup fails with the following error message on the console:

Error! Failed to initialize the database (exit value was 1). Exiting..

The installation of the Master Server is incomplete. It can be removed by using the following command:

# pkgrm SUNWspsms SUNWspsc1

Also the db error log would contain a message similar to the following:

IpcMemoryCreate: shmget(key=5432001, size=426688512, 03600) failed: Not enough space

It is recommended, to stop all other processes that might be using shared memory during master server installation. If the master server could not be installed even after upgrading the physical RAM, refer to Chapter 11, Upgrading to the Sun N1 Service Provisioning System 6.0, in Sun N1 Service Provisioning System 6.0 Installation Guide. This chapter describes the steps required to migrate the Master Server from this machine to a different one that meets the minimum system requirements.

Workaround: The workaround for this issue is to increase the physical RAM on the system. The Master Server cannot be installed on systems that do not meet the minimal system configuration requirements.

The minimal system configuration requirements for Master Server are documented at Master Server Hardware Requirements in Sun N1 Service Provisioning System 6.0 Installation Guide.

Also, if Master Server installation was successful, but fails to start up due to shared memory constraints, the shared memory requirement of the Master Server could be reduced by using one, or both, of the following methods:

Windows: Installation Fails When User Does Not Have Correct Privileges or Incorrect Password Is Entered (6394017)

The user is installing a Master Server, Remote Agent, or Local Distributor on a Windows system. If the user chooses to run the Windows Service as Other Account, the user needs to provide a username that has Log on as a service privileges. If the user types an invalid password or the username does not have Log on as a service privileges, the installed services fail to start.

When the services fail to start, one of the following error messages is displayed:

This error occurs because the user typed an invalid password or the username does not have Log on as a service privileges. Username validation only validates the existence of the user on that computer. The credentials are not checked to see if the password is valid for that user or if the username has "Log on as a service" privileges.

Workaround: To prevent this error, implement one of the following workarounds: