Workaround: Install the following packages before installing Sun Management Center.
SUNWsprot
SUNWpostgr-pl
SUNWpostgr-devel
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 |
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:
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
svcadm disable sunmcdatabase
/opt/SUNWsymon/sbin/es-start -A
Workaround 2: Type the following commands:
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
svcadm disable sunmcdatabase
/opt/SUNWsymon/sbin/es-start -A
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.
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.
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:
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.
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 |
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 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, type 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.
Workaround: Unload the Fault Manager Plug-in manually using the fmadm command before uninstalling the agent. The steps are as follows:
Unload the libfmalm module by typing fmadm unload libfmalm.
Uninstall the agent by typing es-uninst -X.