HP Insight Cluster Management Utility - Manual (Page 126)

A Troubleshooting
Issues encountered while using HP Insight CMU can be classified as:
•
Network boot issues which affect cloning and backup
•
Backup specific issues
•
Cloning specific issues
•
Administration command issues
•
GUI specific issues
A.1 HP Insight CMU logs
Every HP Insight CMU command logs information in a dedicated log file. All log files are available
in /opt/cmu/log.
A.1.1 cmuserver log files
When using the GUI, all actions executed on the cluster are sent to the cmuserver daemon
running on the management node. The /opt/cmu/log/cmuserver-0.log file on the
management node contains the current output of the cmuserver process. Results of the command
/etc/init.d/cmu
option are logged to /var/log/cmuservice_hostname.log where
hostname is the hostname of the HP Insight CMU administrator node.
A.1.2 Cloning log files
All cloning log files are available on the management node. After cloning, the /opt/cmu/log/
cmucerbere.log
file contains the output of the cloning daemon running on the management
node. This file contains a summary of the entire cloning process.
The /opt/cmu/log/cmucerbere-NodeXXX.log file contains detailed cloning output for each
node.
NOTE: The cmucerbere-NodeXXX.log files are updated on the management node 3 minutes
after cloning completes.
A.1.3 Backup log files
All backup log files are available on the management node. After backup, the /opt/cmu/log/
cmudolly.log
file contains the output of the backup client running on the management node.
The /opt/cmu/log/cmudolly-NodeXXX.log file contains the output of the backup daemon
running on the compute node.
A.1.4 Monitoring log files
On the management node, the /opt/cmu/log/MainMonitoringDaemon_MGTXXX.log file
contains the output of the monitoring daemon running on the management node. On each compute
node, the /opt/cmu/log/SmallMonitoringDaemon_NodeXXX.log file contains the output
of the monitoring daemon running on the compute node. On each compute node designate as the
secondary server for the network entity, the /opt/cmu/log/
SecondaryServerMonitoring_NodeXXX.log
file contains the output of the HP Insight CMU
Secondary Server process.
A.2 Network boot issues
Nodes might not boot in the network mode due to one of the following causes:
•
A hardware issue on the node
•
A network issue with the network cable, switch port, or the NIC
126 Troubleshooting