Start Script Might Display Could not start Grouping service or Could not start Platform Agent Error Message (4851517)

If Sun Management Center components are started on a heavily loaded machine, the following error message might be displayed:

Could not start Component

In addition, if a particular component process does not start within a specific amount of time, the start script might display the same error message, even if the component was successfully started.

This problem has been observed for both the Grouping service and the Platform Agent components.

The start script has the following actions:

• Attempts to start the component process

• Sleeps x seconds

• Checks the process status and report success or failure

A heavily loaded machine can delay the results of the status check, which results in an erroneous status check failure. The error occurs because the results were not received within x seconds.

Workaround: Complete the following workaround:

1. Use the /usr/bin/ps -eaf | grep esd command to verify whether the following processes are running:

   • Agent

   • Topology service

   • Trap-handler service

   • Configuration service

   • Event-handler service

   • Metadata service

   • Platform Agent

   • Instances of Platform Agent

2. Use the /usr/ucb/ps —wwxa | grep SunMCService command to verify whether the Grouping service is running.

3. Use the /usr/ucb/ps —wwxa | grep java | grep ServerMain command to verify whether the Java server is running.

4. Use the /usr/ucb/ps —wwxa | grep java | grep tomcat command to verify whether the Web server is running.

5. Use the /usr/ucb/ps —wwxa | grep java | grep HWDS command to verify whether the the Hardware Service is running.

If a service is not running, reduce the machine load, and restart the Sun Management Center processes.