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.