Managing HP Serviceguard A.11.20.00 for Linux, June 2012
Messages
The coordinator node in Serviceguard sometimes sends a request to the quorum server to set the
lock state. (This is different from a request to obtain the lock in tie-breaking.) If the quorum server’s
connection to one of the cluster nodes has not completed, the request to set may fail with a two-line
message like the following in the quorum server’s log file:
Oct 008 16:10:05:0: There is no connection to the applicant
2 for lock /sg/lockTest1
Oct 08 16:10:05:0:Request for lock /sg/lockTest1 from
applicant 1 failed: not connected to all applicants.
This condition can be ignored. The request will be retried a few seconds later and will succeed.
The following message is logged:
Oct 008 16:10:06:0: Request for lock /sg/lockTest1
succeeded. New lock owners: 1,2.
Lock LUN Messages
If the lock LUN device fails, the following message will be entered in the syslog file:
Oct 008 16:10:05:0: WARNING: Cluster lock lun /dev/sdc1 has failed.
Troubleshooting Serviceguard Manager
The following section describes how to troubleshoot issues related to Serviceguard Manager
SolutionProblem
Ensure that a loop back address is mentioned in the /etc/
hosts file 127.0.0.1 localhost.localdomain
localhost
“Service Temporarily Unavailable” when trying to launch
Serviceguard Manager
Run the Tomcat startup command
/opt/hp/hpsmh/tomcat/bin/startup.sh
Tomcat process has not started by any chance
The following message is displayed when erviceguard
Manager is launched from HP System Management Home
1. Install the pre-requisite version of Java(1.6 or later) and
Tomcat(5.x or 6.x)
(SMH) web page, if Java and/or Tomcat versions are not
as per the pre-requisite:
2. Ensure /usr/bin/java is pointing to supported
version of Java ("ll /usr/bin/java" ). Otherwise, unlink
Service Temporarily Unavailable or Http
status 500 proxy error or SMH can't find the
requested page
unlink /usr/bin/java and create a new link ln
-s <full path of JAVA installation
directory> /usr/bin/java
3. Ensure /usr/share/sgmgr-tomcat points to tomcat
installation directory, that is, catalina_home ( "ll
/usr/share/sgmgr-tomcat"). Otherwise, unlink
unlink /usr/share/sgmgr-tomcat and create
a new link ln -s <full path of Tomcat
installation directory>
/usr/share/sgmgr-tomcat
4. Ensure Serviceguard-manager-tomcat rpm is
installed ("serviceguard-manager-tomcat-01.00-0"
should be listed in execution of the command "rpm -qa
| grep serviceguard")
5. Run /opt/hp/hpsmh/tomcat/bin/tomcat_cfg
script
238 Troubleshooting Your Cluster