HP Servicecontrol Manager 3.0 Troubleshooting Guide

Chapter 1
7
1 Troubleshooting SCM
This chapter provides general information on diagnosing issues associated with
Servicecontrol Manager (SCM).
Complete steps 1
-5 on the central management server (CMS) to diagnose the specific
problems you are experiencing. Follow step 6
to verify and resolve the specific problems.
To Diagnose Issues with SCM
Step 1. Check for errors in the following log files.
• /var/opt/mx/logs/mx.log
• /var/opt/mx/logs/MySQLInstall.log
• /opt/hpwebadmin/logs/catalina.out
• For HP-UX: /var/adm/syslog/syslog.log
For Linux: /var/log/messages
Step 2. Verify that the required daemons are running.
/opt/mx/lbin/mxdtf
/opt/mx/lbin/mxdomainmgr
/opt/mx/lbin/mxagent
Step 3. Verify that the Tomcat Web server is running.
ps -fp $(cat /opt/hpwebadmin/logs/.tomcat.pid)
Step 4. Log on to the CMS and run the following simple commands.
mxnode
mxexec -t df -n
cms
mxexec -t df -n node
where cms is the hostname of the CMS and node is the hostname of a managed node.
Step 5. Log on to the SCM graphical user interface (GUI) and verify basic functionality.
a. Verify that the nodes list is populated with valid nodes.
b. Verify that the tools menu appears with valid tools when you select a node from the
nodes list
c. Run df in the General Tools category on the selected node.
If this tool isn’t available, select another command line tool to run instead.
d. Run View Properties in the View category on the selected node.
If this tool isn’t available, select another Web tool to run instead.
e. Run Accounts for Users and Groups in the System Administration category on
the selected node.
If this tool isn’t available, select another X Window tool to run instead.