Sun N1 Service Provisioning System 5.2.1 Release Notes

Installation Issues

This section describes known issues with installation.

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 5.2 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:

File path provided for the keystore file is invalid
The password given is not a valid password for the keystore file

Workaround: To prevent an error, verify the following:

The file path is valid and is accessible
The file type is a valid keystore file
The password provided for the keystore file is valid

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 5.2 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 10, Upgrading to the Sun N1 Service Provisioning System 5.2, in Sun N1 Service Provisioning System 5.2 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 5.2 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:

Reduce the max_connections and shared_buffers parameters in the postgres configuration file $BASEDIR/N1_Service_Provisioning_System_5.2/server/postgres/data/postgresql.conf. Set max_connections to 32 and shared_buffers to 8,000.
Reduce the db.maxconnections property in the $BASEDIR/N1_Service_Provisioning_System_5.2/server/config/config.properties file to 30.

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:

Master Server

After reboot, the installation will fail because the database setup requires that the postgres services are running. Since the credentials given for the Other Accountare invalid, the postgres service fails to start, the installation hangs, and the following error message is displayed:

At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
Remote Agent

Error 1920.Service cragent (cragent) failed to start. Verify that you have sufficient privileges to start system services.
Local Distributor

Error 1920.Service crdistributor (crdistributor) failed to start. Verify that you have sufficient privileges to start system services.

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:

Verify that the password to be entered for the Other Accountis valid and that the username has Log on as a service privileges.
Select the System Account option instead of the Other Account option. In this case, the user is not required to provide a username or password. The installation will continue and the services will run under the SYSTEM user.