HP Servicecontrol Manager 3.0 Troubleshooting Guide
Troubleshooting SCM
Chapter 1
8
Step 6. Identify the applicable issue in one of the following chapters to troubleshoot and resolve
your problem. Use the data collected in the previous steps to determine which issues
may apply.
• Operating System and Networking Issues
See Chapter 2, “Operating System and Networking Issues,” on page 11. This chapter
covers the following issues:
— “Agent Unable To nslookup The CMS Hostname” on page 12
— “Authentication Failures Due To Time Synchronization Or Communication Time
Limits” on page 12
— “CMS Unable To nslookup Node Hostname” on page 12
— “File Related Errors” on page 13
— “Hardware Problems (Such As LAN Card Failures)” on page 14
— “Incorrect Network Configuration” on page 15
— “Insufficient File System Space In /var” on page 16
— “Insufficient Kernel Resources” on page 16
— “Insufficient Swap Space” on page 17
— “Problems With getpwnam()/uid()” on page 18
— “Problems With resolv.conf, hosts, nsswitch” on page 19
— “SuSE System Information Missing” on page 20
— “SuSE CMS Reporting An IP Address Instead Of A Hostname” on page 20
— “Web Server Not Running” on page 21
• Servicecontrol Manager Issues
See Chapter 3, “Servicecontrol Manager Issues,” on page 23. 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
— “Management Home Page Is Already Open” on page 25
— “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