Start script might display error messages like Could not start Grouping service or Could not start Platform Agent.
You might see these error messages when you run the es-guiinst command on the Sun Fire system controller or when the Sun Management Center components are started on a heavily loaded machine.
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 does the following actions:
Attempts to start the component process
Sleeps n seconds
Checks the process status and reports 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 n seconds.
Workaround: Complete the following workaround:
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
Type the following command:
/usr/bin/ps -ef | grep esd |
(On Solaris 10) The command would be /usr/bin/ps -fz global | grep esd on a global zone and /usr/bin/ps -fe | grep esd on a non-global zone.
To verify whether the Grouping service is running, type the following command:
/usr/ucb/ps —wwxa | grep SunMCService |
To verify whether the Java server is running, use the following command:
/usr/ucb/ps —wwxa | grep java | grep ServerMain |
To verify whether the web server is running, type the following command:
/usr/ucb/ps —wwxa | grep java | grep tomcat |
To verify whether the Hardware Service is running, type the following command:
/usr/ucb/ps —wwxa | grep java | grep HWDS |
If a service is not running, reduce the machine load and restart the Sun Management Center processes.