Chapter 1 Installation Issues

Issues include information that you should know about, such as prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues. Bugs have tracking numbers shown in parentheses. For updates on bugs and for patches, see the SunSolve^SM web site at http://sunsolve.sun.com.

Installation Bugs

Solaris Container Manager Installation Fails on Solaris 10 End User Distribution (6722204)

Workaround: Install the following packages before installing Sun Management Center.

• SUNWsprot

• SUNWpostgr-pl

• SUNWpostgr-devel

Login to Sun MC 4.0 Server Fails if Re-installed at a Different Location (6621376)

Re-installation of Sun MC 4.0 in a location other than the one chosen during the first time installation causes Sun MC topology and event services to fail. Because of the failed topology service, users will be unable to log in. Logging in to Sun MC 4.0 server by Web Console or Client APIs will also fail.

The following error message is displayed:

The Sun Management Center server is being initialized.
Retry

This bug is caused because of symbolic links present under the /usr/local/etc directory for the ODBC.ini file. The symbolic link files do not get updated to the new installation location and still point to the previous installation location.

Workaround: If there are no other Open Database Connectivity (ODBC) dependant applications, then type the following commands:

#es-stop -A
#cd /usr/local/etc
#ln -s  <INSTALLDIR>/SUNWsymon/odbc/etc/odbcinst.ini odbcinst.ini
#ln -s  <INSTALLDIR>/SUNWsymon/odbc/etc/odbc.ini odbc.ini 
#es-start -A

If an ODBC dependant application is installed after the Sun MC 4.0 server is installed then the new application might overwrite the Sun MC ODBC information. In such a case, type the following commands:

#es-stop -A
#cd /usr/local/etc
#cat <INSTALLDIR>/SUNWsymon/odbc/etc/odbcinst.ini >> odbcinst.ini
#cat <INSTALLDIR>/SUNWsymon/odbc/etc/odbc.ini >> odbc.ini
#es-start -A

Database Startup Fails After Incremental Installation (6615279)

After an incremental installation of the server, console, Advanced System Monitoring (ASM) Modules, Common Config Reader, and Desktop add-ons, database startup fails. The following error message is displayed:

Failed to start database

Workaround 1: Type the following commands:

1. Give read permissions to the group and others for the /var/opt/SUNWsymon/db/data/SunMC/pg_hba.conf file:

   usr/bin/chmod go+r /var/opt/SUNWsymon/db/data/SunMC/pg_hba.conf

2. svcadm disable sunmcdatabase

3. /opt/SUNWsymon/sbin/es-start -A

Workaround 2: Type the following commands:

1. Change the owner and group of the /var/opt/SUNWsymon/db/data/SunMC/pg_hba.conf file to smcdbu and smcdbg respectively:

   usr/bin/chown smcdbu:smcdbg /var/opt/SUNWsymon/db/data/SunMC/pg_hba.conf

2. svcadm disable sunmcdatabase

3. /opt/SUNWsymon/sbin/es-start -A

Link Icon Remains on the Windows XP Desktop After Sun MC Console Installation Is Uninstalled (6603045)

When Sun Management Center 4.0 is installed on any Windows XP node, the console launch icon remains on the Desktop even after the product is uninstalled. No error message is displayed.

• Workaround 1: Uninstall Sun MC 4.0 using the SunMCUninst.bat file in the INSTALL_DIR/SUNWsymon/SunMC4.0/install directory.

• Workaround 2: Remove the link manually.

• Workaround 3: Use Java Web Start—based console to launch the Sun Management Center Java console and not deploy it locally.

Cannot Install Sun MC on 32–bit SLES 10 (6587289)

Sun MC cannot be installed on a 32–bit SUSE Linux Enterprise Server (SLES) 10 system. The following error message is displayed:

# ./es-start -a
couldn't load file "pkgsymon.so": libgdbm.so.2: 
cannot open shared object file: No such file or directory
invalid command name "unordered_slice"
    while executing
"unordered_slice internal value"
    invoked from within
"source toe-basic.toe"
    invoked from within
"source base-$file.tcl"
--- 

Workaround: Prior to installing Sun MC, download the gdbm-1.8.0-24.i386.rpm old library package. Install the package using the rpm -i --oldpackage gdbm-1.8.0-24.i386.rpm command. Proceed with installing Sun MC on the 32–bit SLES 10 system.

Installation on SLES9 SP3 And FC 4.0 Machines Displays Missing Library Files Message (6572715)

Some libraries are missing during the installation of the SUN MC 4.0 release on the SLES9 SP3, 32-bit and 64-bit, and FC 4.0 64-bit Linux platforms. Missing library files messages are displayed.

Workaround: Perform the following steps:

1. Download and install the following packages and libraries:

   • On 32-bit SLES9 SP3– Install or upgrade the libgcc-3.4.6-8.i386.rpm package. Install the missing libstdc++-3.4.6-8.i386.rpm library before installing the Sun MC agent.

   • On 64-bit SLES9 SP3 – Install or upgrade the libgcc-3.4.6-8.x86_64.rpm package. Install the missing libstdc++-3.4.6-8.x86_64.rpm library before installing the Sun MC agent.

2. Type the following command:

   ln -s /usr/lib64/libstdc++.so.6 /usr/lib/libstdc++.so.6

   For 64-bit FC 4.0 systems, type the following command:

   ln -s /usr/lib64/libdb-4.3.so /usr/lib/libdb-4.3.so

Cannot Install Sun MC on 64–bit SLES 10 (6566864)

Sun MC cannot be installed on a 64–bit SLES 10 system. This issue occurs because a few libraries are missing from the 64–bit SLES 10 system. The following error message is displayed:

----------------------------------------------------------------------------
This script installs Sun (TM) Sun Management Center 4.0
----------------------------------------------------------------------------
Installation files source directory: 
<source_dir>/disk1/image/Linux/x86
/bin/chmod: cannot access 
`/var/opt/SUNWsymon/install/Registry_snqa-v20z-13.xml': No such file or directory
Unable to create Registry 
/var/opt/SUNWsymon/install/Registry_snqa-v20z-13.xml.

Exiting Sun Management Center 4.0 installation.

Workaround: Prior to installing Sun MC, download the following packages:

• libxml2-32bit-2.6.23-13.x86_64.rpm – Mandatory package

• zlib-32bit-9.3-7.2.x86_64.rpm – Mandatory package

• db42-32bit-9.3-7.x86_64.rpm – For agent installation

• compat-gdbm-1.8.0-5.i586.rpm – To start the agent

Install these packages using the rpm -i package-name command. Proceed with installing Sun MC on the 64–bit SLES 10 system.

Start Script Might Display Error Messages (4851517)

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:

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 -ef | grep esd

   ---

   Note –

   (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.

   ---

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, type 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.

Uninstallation Hangs While Trying to Uninstall Agent and Base Add-ons Together in Solaris10 6/06 System

Workaround: Unload the Fault Manager Plug-in manually using the fmadm command before uninstalling the agent. The steps are as follows:

1. Unload the libfmalm module by typing fmadm unload libfmalm.

2. Uninstall the agent by typing es-uninst -X.

Installation Information That Applies to the Add-On Software for Sun Fire Entry-Level Midrange Systems

Installing Sun Management Center 3.6 Version 3 Add-On Software for Sun Fire Entry-Level Midrange Systems: Required for Netra 1290 Systems

If you are installing the add-on software for Sun Fire entry-level midrange systems, release 3.6 Version 3 is strongly recommended.

For support of Netra 1290 systems, release 3.6 Version 3 is required. Even if you have previously installed the release 3.6 Version 3 add-on software, you must install it again after installing the core 4.0 software.

To Install Sun Management Center 3.6 Version 3 Add-On Software

1. When installing the Sun Management Center 4.0 software, do not install the Sun Fire Entry-Level System product.

2. After you have installed the Sun Management Center 4.0 software, obtain the Sun Management Center 3.6 Version 3 add-on software.

   The add-on software packages are supplied in a zip file on the software download site at http://wwws.sun.com/software/download/index.html

   If you do not see the listing for Sun Management Center 3.6 Version 3 under New Downloads, use the A-Z Index of All Products to find the software.

   Refer to the Sun Management Center 3.6 Version 3 Add-On Software Release Notes for Sun Fire Entry-Level Midrange Systems for information about installing this release.

   The release notes document is available at http://docs.sun.com/

   Follow the instructions in the section “Updating From Sun Management Center 3.6 Software,” replacing references to the core Sun Management Center 3.6 software with “4.0.”

Internationalization and LocalizationBugs That Occur During Installation

Software License Agreement and Supplemental Terms and Conditions for Some Asian Locales Are in English Language (4874523)

During installation, the Software License Agreement (SLA) and Supplemental Terms and Conditions for the following Asian locales are in English language:

The following Asian locales use localized SLA files and are in the appropriate languages.

To read the SLAs in all supported languages, refer to the printed license that is included in the Sun Management Center media kit.

Workaround: None.

Installation Messages Not Displayed Completely on Localized Environment When Using es-guiinst (4841202)

When you use the es-guiinst command to install on Asian locales, installation messages on some of the screens are not completely displayed. This problem also occurs in the English locale when larger system font sizes are used.

Workaround: Manually size the screen to display the text or maximize the screen to display the text.

Internationalization and Localization Bugs Relating to the Web Console

Properties for Generic x86Config Reader are Not Localized (6602094)

The properties of the x86 Config Reader are not localized. Log in to the Web Console-based browser interface in a Solaris x86 system. Select a host machine in the Monitor tab. Expand Hardware and Generic X86/X64 Config Reader nodes. The following objects are displayed in English:

• IPMI User

• BMC Inventory

• Chassis Status

• Sensor Info

• System Event Log

All the property tables under each object are also displayed in English:

Workaround: None.

hostname:8080/index.html Is Not Localized (6599709)

The hostname:8080/index.html file is not localized. When logging in to http://hostname:8080, the new index.html for Sun MC 4.0 is displayed in English. If you click Launch Webstart, the Sun Management Center login window is displayed in English. But after logging in successfully the main window is localized.

Workaround: None.

Content of Host Details Panel Might Appear in English in Localized Browser Interface (6595364)

Some parts of the localized Web Console—based browser interface, such as contents of the Host Details panel might appear in English.

Workaround: None.

Sun MC Online Help Does Not Appear in the Browser's Language (6594720)

When the browser language is ja, fr, or ko, the Sun MC Online Help is not displayed in the browser's language. The Online Help is displayed in the language or locale defined in the /etc/default/init file of the server system.

Workaround: Perform the steps as described in the Workaround of Parts of Web Console-based Browser Interface Do Not Reflect the Browser's Language Change (6582535).

Parts of Web Console-based Browser Interface Do Not Reflect the Browser's Language Change (6582535)

Some parts of the Web Console-based browser interface are not displayed in the language selected in the browser. They are displayed in the language or locale defined in the /etc/default/init file of the server system.

Workaround: Before installing the Sun MC 4.0 software, ensure that the language or locale defined in the /etc/default/init file of the server system is the same as what you want to use with the browser. After installation, you can change the locale in the /etc/default/init file to the desired language. To change the locale after installation, perform the following steps:

1. Edit the /etc/default/init file of the server system and define the desired language or locale using the LANG=<locale> variable. For example, use LANG=ja for the ja locale, LANG=fr for the fr locale, LANG=ko for the ko locale, LANG=zh for the zh locale, LANG=zh_TW for the zh_TW locale, and so on. Delete or comment out the original locale setting.

   ---

   Note –

   Alternatively, LC_* variables can also be used to set the desired locale.

   ---

2. Reboot the server system.

3. After the server system reboots, you might need to start the SMC Webserver by using the /usr/sbin/smcwebserver start command.

4. Select the desired browser language in the Edit -> Preferences -> Languages menu. You might also need to clear up the browser's cookies and cache.

5. Log in to the browser interface at https://hostname.domain:6789 to confirm the language setting.

Internationalization and Localization Information That Pertains to Sun Management Center 4.0 Add-On Products

Supported Languages and Locales for Sun Management Center 4.0 Add-On Products

The supported languages and locales for the following Sun Management Center 4.0 add-on software products are listed in Table 1–1:

• Sun Fire^TM high-end systems

• Sun Fire midrange systems

• Sun Fire entry-level Midrange systems

• Workgroup servers

• Workstation (desktop) systems

• Netra^TM servers

• Sun Blade^TM and Sun Fire entry-level platform systems