HP Servicecontrol Manager 3.0 Troubleshooting Guide

Servicecontrol Manager Issues
SCM Fails On Startup With No Error Messages
Chapter 3
35
— If the file was moved to another directory and you can locate the correct file,
move it back to the appropriate directory. Alternatively, if there is a backup from
which the original file can be retrieved, restore it.
— If the file was deleted, reconfigure the CMS:
mxinitconfig -a all
CAUTION Reconfiguring the CMS may cause data loss; make sure you have a backup.
• Remote Exception or Malformed URL
SCM may throw a remote exception or malformed URL exception if it is unable to
bind with the RMI registry. Make sure the mxagent daemon is running:
ps -ef | grep mxagent
If mxagent failed to start, look for system log entries pertaining to init. The init
syslog entries may indicate what is preventing mxagent from starting correctly.
To quickly locate these, use the command:
—For HP-UX: grep init syslog.log
— For Linux: grep init messages
• Failed To Find mx.properties File
SCM may not be able to locate the mx.properties file in the /etc/opt/mx/config
directory. Make sure the file exists and has appropriate permissions.
If the file does not exist, it may have been inadvertently moved or deleted.
—If the mx.properties file was moved to another directory and you can locate the
correct mx.properties file, move the file back to /etc/opt/mx/config.
Alternatively, if there is a backup from which the original mx.properties can be
retrieved, restore it.
— If the file was deleted, reconfigure the CMS:
mxinitconfig -a all
CAUTION Reconfiguring the CMS may cause data loss; make sure you have a backup.