test

Sun Management Center 3.5 Release Notes

Installation Bugs

Installation Guide Patch-Only Procedures Produce Extra-Large Image (4858591)

If the directory for the patch image is created at the root level, as described by the Sun Management Center 3.5 Installation and Configuration Guide, the image tool includes the Sun Management Center /sbin and /lib subdirectories in the patch-only image. The result is that a larger than necessary patch image is created. The /sbin and /lib directories are not needed for a patch-only image.

Workaround: To avoid this problem, follow these steps.

  1. Create the following directory structure on the machine:


    /disk2/image/Patches/Solaris_2.6
..                  /Solaris_7
..                  /Solaris_8
..                  /Solaris_9

  2. Download and uncompress the patch files.

  3. Place the patch in the appropriate Solaris directory.

  4. Run the image tool. When prompted for the installation files source directory, specify /disk2/image.

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:

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.

es-makeagent Command Does Not Work From CD Image (4863944)

The es-makeagent command will not run from the CD or a CD image. The command issues the following error message and then exits to the system prompt:


You have called es-makeagent from the cd image.
/var/run/tmp/SunMCInstall/sbin/es-makeagent: illegal option -- L

Workaround: Run the es-makeagent command from the machine on which you have installed the Sun Management Center server. Use the following command:


# /opt/SUNWsymon/sbin/es-makeagent

where /opt is the directory where Sun Management Center 3.5 was installed. If you installed Sun Management Center 3.5 in a different directory, substitute /opt with the name of the top-level directory where you installed Sun Management Center.