Installation Bugs

Cannot Install Sun Management Center 3.5 Update 1 on Windows 98 Platform from CD-ROM (5035612)

When you install Sun Management Center 3.5 Update 1 on the Windows 98 platform, you receive an error message that it cannot find localization files. On Windows 98 the SYSTEMDRIVE variable needs to be set in the autoexec.bat file for the value of this variable to be accessible on the MS-DOS prompt. For Sun Management Center 3.5, the installer used to assume C: would be the default Microsoft Windows installation directory and drive. But on machines where the system drive is something other than C:, the installer fails.

To eliminate this issue, the installers were enhanced to detect the Microsoft Windows installation drive and proceed with this drive instead of assuming C: drive as the installation directory and drive. On other Microsoft Windows operating systems, the default installation drive and directory are available at the MS-DOS prompt. But for Windows 98 the default drive is not defined.

Workaround: You have several options:

• For the installer to work from the CD-ROM for Windows 98, set the SYSTEMDRIVE variable. Use the command SET SYSTEMDRIVE = X: where X is the actual drive where Windows 98 has been installed.

• Copy the CD-ROM to the hard disk and run the installer from there.

• Install by uncompressing the winImage.tar file from the Sun Management Center 3.5 Update 1 web page on the following web site: http://wwws.sun.com/software/download

Using the JumpStart Script from Previous Sun Management Center Releases Fails to Install the x86 Agent and Shows an XML Library Message (5030308)

Using the JumpStart^TM script from previous Sun Management Center releases fails to install the x86 agent and produces an XML library message. Because of differences between SPARC and x86 architecture, you might see these messages:

WARNING: Cannot determine the hostname on /a using default registry name
Registry_localhost .xml SML shared object library not accessible

Workaround: None.

es-inst -R Command With Documentation Fails When SUNWsdocs Does Not Exist on Remote Host (5025112 )

If the remote server does not have the documentation package SUNWsdocs, installing the Sun Management Center 3.5 Update 1 server layer on a remote machine might fail.

The command es-inst —R /net/remote_server fails when you add the documentation package SUNWpsmd. Because the package SUNWpsmd depends on SUNWsdocs, if SUNWsdocs is missing, the installation exits.

Workaround: Make sure the remote server has the SUNWsdocs package installed before installing the Sun Management Center 3.5 Update 1 documentation.

Installation From CD or CD Image Requires Full Path for es-inst script (4975862)

When you install Sun Management Center 3.5 or Sun Management Center 3.5 Update 1, you must give the full path for the es-inst script. Running the es-inst script from the /cd-image-dir/disk1/sbin directory or /cdrom/cdrom0/sbin directory does not work. If you change the directory to /cdrom/cdrom0/sbin and give the complete path, the script does not work. Your working directory should not be /cdrom/cdrom0/sbin.

Workaround: If you are installing from the CD, change to the root directory (/) and type the full path:

# cd /
# /cdrom/cdrom0/sbin/es-inst

# cd /
# /cd-image-dir/disk1/sbin/es-inst

Start Script Might Display Error Messages: Could not start Grouping service or Could not start Platform Agent (4851517, 5016981)

You might see these error messages when you run the es-guiinst command on the Sun Fire 15K system controller or when the 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 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:

1. 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 -eaf | grep esd

2. To verify whether the Grouping service is running, type the following command:

   /usr/ucb/ps —wwxa | grep SunMCService

3. To verify whether the Java server is running, use the following command:

   /usr/ucb/ps —wwxa | grep java | grep ServerMain

4. To verify whether the web server is running, type the following command:

   /usr/ucb/ps —wwxa | grep java | grep tomcat

5. To verify whether the Hardware Service is running, type the following command:

   /usr/ucb/ps —wwxa | grep java | grep HWDS

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