-

Chapter 7-

Troubleshooting CST

Because CST is a client-server application, the communication between the applet, the server, and the agent on the host being tracked can be unstable. This may be because either the host or the server or the CST daemon processes in them may be down momentarily. This chapter lists error messages and possible solutions.

Send comments to the CST Development Team by clicking on the Comments button at the bottom of the CST GUI.

Note - You must run Netscape Communicator in order to use the Comments button, since Netscape Navigator does not support an email capability. If using Netscape Navigator, send email to cst-master@eng.sun.com.

Error Messages

CST Launch Error in Sun Management Center Environment

Problem: Cannot launch CST console and following error message displayed from Console Message Window:

from stdout Jul 18 10:34:13 AWT-EventQueue-0:

SNMP request returned error status 17 (not writable)

	......

	......

Suggested action: As superuser within the Sun Management Center server, stop the server, move the file the system is not detecting, and restart the server. Type:

/opt/SUNWsymon/sbin/es-stop -x

mv /var/opt/SUNWsymon/cfg cstservice-modules-d.dat cstservice-modules-d.dat.org

/opt/SUNWsymon/sbin/es-start -x

Start the Sun Management Center console and load CST 3.5.

Wrong Component (Agent vs Server) Selected During Install

Problem: The agentcomponent was selected during the installation.

Suggested action: To get the Server/Agent option back into the installation, you must remove the existing CST package using pkgrm. Then manually clean up the directory, /var/opt/SUNWcst and reinstall the CST package.

Note - This action must be taken only in the case of a fresh install.

CST Package Install Fails - Repository is a Sub-folder in /var/opt/SUNWcst

Problem: The CST package install fails when the database repository is a sub-folder in /var/opt/SUNWcst.

Suggested action: Create the folder for the databse repository outside of /var/opt/SUNWcst. If one or more of the CST agents are attached to this agent, the move could affect the functioning of the attached agents.

Note - See the CST Administration chapter, the To Move Agent Data to a Different Hierarchy, section for details.

Error in Compiling Statistics

Problem: In the statistics folder the Total Time prints out an Error message like the following one:

ERROR: Time stamp incorrect on event #25

Suggested action: To fix the offending event details, call your local Sun service provider.

Site Registration Fails With Customer ID and Key

Problem: Registration fails when the provided customer ID and registration key is used in the CST console.

Suggested action: This can happen if the registration key is used on a system that is different from the one that sent out the registration request. Request a new registration key from the system generating the error.

Note - The registration key is based on the hostid and must be used only on the system for which it is generated.

Cannot View FRUI Data on SF15K SC

Problem: Sometimes the FRU data on the SF15K system controller is not available to view.

This is often because the FRU information is still being gathered by CST.

Suggested action: It is also possible that, in the process of probing, a CST FRU probe consumes a lot of system resources. If you want to turn off this feature, set the parameter, SF15K_FRU_INTERVAL to 0 in the cst.conf file, then restart CST. For more details and the syntax of the cst.conf file, refer to the CST Administration chapter, the Tuning CST Trigger Intervals section.

Missing FRU Data for Mid-frame Sun Fire System Controllers

Problem: This may happen if the (required) library, libfrurmi.so, and other related files are not in the paths searched by CST.

Sun Fire mid-frame systems are Sun Fire 3800, 4800, 4810, and 6800.

Suggested action: Locate the library, libfrurmi.so, and related files and modify the script in /opt/SUNWcstve/bin/cstrfru_start.sh. Remember that this applies only to the SUNWcstve package files.

For example:

If the libfrurmi.so and related files are in the directory, /opt/SUNWfrusg/lib, then change the script to:

#!/bin/sh

CSTVAR=/var/opt/SUNWcst

CSTBIN="`dirname $0`"

if [ -f "/opt/SUNWfrusg/lib/libfrurmi.so" ]; then

LD_LIBRARY_PATH=/opt/SUNWfruid/lib:/opt/SUNWfrusg/lib:${LD_LIBRARY_PATH}

        export LD_LIBRARY_PATH

        ${CSTBIN}/cstrfru $1 $2 $3 $4 $5 $6

else

        echo "cannot find shared object libfrurmi.so" > /tmp/cstrfru.err

fi

CST Platform Data Missing on Sun Fire 15K Main SC

Problem: CST platform data is missing on Sun Fire 15K MAIN system controller. This might be because the root user is not in any of the platform groups, such as platadmn, platoper, and platsvc.

Suggested action: The fix is to modify /etc/group and add root user to one of the platform groups. This can be verified by running the command, showfailover -r, as root. The command should return either MAIN or SPARE. It should not return any errors about insufficient platform privileges.