Building an HP SIM 5.x server on a Linux-based Serviceguard Cluster (444847-001, February 2007)

Troubleshooting

Finetuning of the HP SIM server

• SELinux issue: If activated, postgreSQL does not start in the cluster script.

You must apply the following patch:

# # diff postgresql.orig postgresql

189c189

< $SU -l postgres -c "$PGENGINE/postmaster -p ${PGPORT} -D

'${PGDATA}' ${PGOPTS} &" >> $PGLOG 2>&1 < /dev/null

---

> su -l postgres -c "$PGENGINE/postmaster -p ${PGPORT} -D

'${PGDATA}' ${PGOPTS} &" >> $PGLOG 2>&1 < /dev/null

• SSH configuration: As the SSH key is stored on the shared storage under

/hpsimlnx/etc/config/sshtools, both nodes of the cluster will be able to use it

undistinguishly.

• SSL certificates: When HP SIM generates a new server certificate, it places a copy in the

sslshare directory for SMH to use so that it has the same SSL server certificate and key

as HP SIM. Depending on which system is active, the SMH certificate will be different,

which can cause some confusion. Therefore, it is necessary to redirect the folder

containing the certificate onto the shared storage and to use only one certificate.

For the primary node:

# /etc/init.d/hpsim stop

# /etc/init.d/postgresql stop

# mkdir /hpsimlnx/etc/opt/sslshare

# mv /etc/opt/hp/ssslhare/* /hpsimlnx/etc/opt/sslshare

# rm –rf /etc/opt/hp/ssslhare

# cd /etc/opt/hp

# ln -sf /hpsimlnx/etc/opt/sslshare sslshare

For the second node, once the shared storage is available to it, do not move the content

of the sslshare directory, simply remove its content by running the following

commands and create the symbolic link :

# /etc/init.d/hpsim stop

# /etc/init.d/postgresql stop

# rm -rf /etc/opt/hp/ssslhare

# cd /etc/opt/hp

# ln -sf /hpsimlnx/etc/opt/sslshare sslshare