HP Servicecontrol Manager 3.0 Troubleshooting Guide

Chapter 3

3 Servicecontrol Manager Issues

Servicecontrol Manager (SCM) depends on a number of daemon processes executing on

the Central Management Server (CMS) and the managed nodes. Failure of the daemons

or failure of communication between the daemons can produce conditions that are not

easily understood.

This chapter covers the following issues:

• “catalina.out Log Fills Up With A Repeated Error” on page 24

• “Command Line Tool Does Not Complete A Task” on page 24

• “Configuration Failure During CMS Update” on page 24

• “mx.properties File Missing” on page 25

• “mxserver.bin Install Error” on page 26

• “Obsolete Tools Migrated from SCM 2.5” on page 26

• “Optional Tools Migrated from SCM 2.5” on page 28

• “Problems With mxexec On A Managed Node (#1)” on page 29

• “Problems With mxexec On A Managed Node (#2)” on page 29

• “Removing A CMS From A Managed Node Fails” on page 30

• “Repository Configuration Failure During Install” on page 31

• “Repository Server Failure” on page 32

• “SCM 2.5 Daemons Not Running During SCM 3.0 Upgrade” on page 33

• “SCM Commands And Manual Pages Are Inaccessible” on page 34

• “SCM Generates A Certificate Error” on page 36

• “SCM GUI Isn’t Available” on page 37

• “SCM Fails On Startup With No Error Messages” on page 34

• “ServiceGuard Manager’s ClusterManagement Tab Missing” on page 37

• “Syntax Problems In The Definition Files” on page 38

• “Management Home Page Is Already Open” on page 25

• “Task Execution From The SCM GUI Fails With No Error” on page 39

• “Tomcat Fails To Start After Removing And Reinstalling SCM” on page 39

• “Tool Ownership Issue” on page 39

• “Tools Only Available On HP-UX 11i v2 Managed Nodes” on page 40

• “WBEM Not Displayed As A Managed Protocol” on page 41

• “Web Launch Tool With Parameters Not Supported” on page 41

• “WLM and PRM Are Not Available Within SCM” on page 42

• “X Window Tool Does Not Run For mxexec” on page 42