HP Servicecontrol Manager 3.0 Troubleshooting Guide

Servicecontrol Manager Issues

SCM Commands And Manual Pages Are Inaccessible

Chapter 3

SCM Commands And Manual Pages Are Inaccessible

When SCM is installed, the default system command shell path and man page path are

updated. If the user has customized their login shell environment, the default paths may

become invalid.

Symptom • Executing a command requires a full pathname, such as: /opt/mx/bin/mxrole -ld

• Retrieving a man page results in the error:

No manual entry for mxcommand

Verification Echo the environment variable for locating commands ($PATH) and verify the path

/opt/mx/bin is not included.

Echo the environment variable for locating manual pages ($MANPATH) and verify the path

/opt/mx/share/man is not included.

Fix Modify the .profile for the shell to update the existing values:

PATH=PATH$:/opt/mx/bin

MANPATH=$MANPATH:/opt/mx/share/man

SCM Fails On Startup With No Error Messages

Symptom SCM fails to start when you first invoke it, and no error messages appear in the

/var/opt/mx/logs/mx.log file.

Fix Check the system log file.

• For HP-UX: /var/adm/syslog/syslog.log

• For Linux: /var/log/messages

To quickly locate Servicecontrol Manager error messages in this log file, use the

command:

• For HP-UX: grep SCM syslog.log

• For Linux: grep mx messages

Possible errors and their remedies follow:

• IO Exception or Error

SCM may throw an I/O exception if it is unable to read the mx.properties file. If

this is the case, the mx.properties filename will be listed in the system log file.

Ensure that the unreadable file exists and has appropriate permissions. The

mx.properties file resides in /etc/opt/mx/config.

If this file does not exist, it may have been inadvertently moved or deleted.