Troubleshooting Tips

Table 6-1 presents troubleshooting problems and the suggested corrective actions.

Table 6-1

Problem	System Display	Corrective Action
Event Generator fails to start properly	"We need the TCL variable Rules to proceed" is displayed in the Event Log file	The upgraded Event Generator is running with an older rules file. Upgrade the event rules by installing the new rules you obtained from the Updates CD (see Chapter 2.)
All agents are displayed in red on the Solstice SyMON console and there are no daemons running on your server	Agents are displayed in red	You may have installed Solstice SyMON agents on an unsupported platform such as an Ultra Enterprise 1 system. Install the Solstice SyMON agents on one of the supported platforms listed in Chapter 1.
Agents are displayed in red on the Solstice SyMON console or no daemons are running on your server	Agents are displayed in red	Check /var/adm/messages for Solstice SyMON-related error messages.

Table 6-1 (Continued)

Problem	System Display	Corrective Action
Solstice SyMON agents are running but the GUI or Event Generator cannot connect to the agents	Event Generator messages will be written to: /var/opt/SUNWsymon/host/EG/ eg_debug.<pid>	Set the debug flag to 4 to trace connectivity; for example: symon -aildebug 4 or in sm_symond.conf, use: sm_egd -D 4 in addition to other arguments.
You are experiencing problems with the Event Generator	(See Corrective Action)	Check for error messages in the Event Generator log file either by using the Log file Viewer or examining this file: /var/opt/SUNWsymon/<host>/EG/event_log
You are experiencing difficulties with the log file scanner	(See Corrective Action)	Check for error messages in the Log file scanner log file either by using the Log file Viewer or by examining this file: /var/opt/SUNWsymon/<host>/LS/ls_log
Solstice SyMON 1.0 and later releases require CDE 1.0.1 and later	"ld.so.1: ./symon: fatal: relocation error: symbol not found: braelist: referenced in /usr/dt/lib/libDtHelp.so.1"	Upgrade your CDE installation to CDE version 1.01 or later; refer to your CDE documentation.
Your system is too heavily loaded	"do_accept : too many open files" appears in the /var/adm/messages file	Close some of the GUIs polling the system
The Event Generator is saturated with polling requests	"get_all_event_string: data not ASCII type ="	Kill and restart the Event Generator; refer to "To Activate New or Modified Event Rules by Stopping and Restarting the Event Generator" in Chapter 4.
Solstice SyMON is installed improperly	A message similar to "ld.so.1: /opt/SUNWsymon/sbin/sm_symond : fatal: libaip.so.1: can't open file: errno=2" appears on the system console or the command terminal	Remove the SUNWsyrt package and install the Solstice SyMON 1.3 SUNWsyrt package (see Chapter 2.)

Table 6-1 (Continued)

Problem	System Display	Corrective Action
Solstice SyMON is installed improperly	When starting the SyMON GUI, a message like "ld.so.1: symon: fatal: relocation error: symbol not found: called_on_incoming_fd_data: referenced in /opt/SUNWsymon/lib/libaip.s" appears	Remove the SUNWsyu package and install the Solstice SyMON 1.3 SUNWsyu package (see Chapter 2.)
Solstice SyMON is installed improperly	When starting the SyMON agents or Event Generator, a message such as "ld.so.1: /opt/SUNWsymon/sbin/sm_symond : fatal: relocation error: symbol not found: called_on_incoming_fd_data referenced in /opt/SUNWsymon/lib/libaip.so" appears on the system console, or the command terminal in /var/adm/messages	Remove the SUNWsys or SUNWsye package and install the Solstice SyMON 1.3 SUNWsys or SUNWsye packages, respectively (see Chapter 2.)
A Solstice SyMON client not running Solstice SyMON 1.3 is attempting to monitor a host running Solstice SyMON 1.3.	When starting the SyMON GUI, a message appear such as "symon: _AIP_request_V14: RPC: Program/version mismatch; low version = XX, high version = XX" where XX is a number greater than 14	Upgrade the client to Solstice SyMON 1.3 (see Chapter 2.)

Table 6-1 (Continued)

Problem	System Display	Corrective Action
The SyMON GUI shows the Event Generator in red. This means the Event Viewer is not accessible.	On the agent host, a message in /var/adm/messages like ... /opt/SUNWsymon/sbin/sm_symond [...]: Version mismatch. Symond on <Event Generator host> is not version 1.3 or on the Event Generator host, a message such as ..../opt/SUNWsymon/sbin /sm_egd[...]: Got an error: <AIL error in /opt/SUNWsymon/sbin/sm_egd: Version mismatch. Symond does not use AIP version 14>	Upgrade the Event Generator host to Solstice SyMON 1.3 (see Chapter 2.)
The SyMON GUI shows the Event Generator in red. This means the Event Viewer is not accessible. The version of Solstice SyMON on the agent host is earlier than version 1.3.	In /var/adm/messages a message such as "... /opt/SUNWsymon/sbin /sm_symond[...]: AIL error in /opt/SUNWsymon/sbin /sm_symond: Version mismatch. Symond does not use AIP version 14 or on the Event Generator host, a message in /var/adm/messages like ... /opt/SUNWsymon/sbin/sm_egd[. ..]: Got an error: <AIL error in /opt/SUNWsymon/sbin/sm_egd: Version mismatch. Symond on <agent host> is not version 1.3>	Upgrade the agent host to Solstice SyMON 1.3 (see Chapter 2.)

Table 6-1 (Continued)

Problem	System Display	Corrective Action
The Solstice SyMON GUI displays unusual colors.	Error messages may be displayed on the system terminal stating that the GUI cannot allocate certain colors.	The shared default color map is full. There are two ways to alleviate this problem: · Make Solstice Symon use a private color map. · Reduce the number of colors used by other applications. To have a private color map for the Physical View images, invoke Solstice SyMON as symon -cm. There may be some color map switching as the cursor focus is moved from the Physical Views to other windows. Each window should display correct colors when the cursor focus is in that window. The main application that uses colors is likely to be Netscape. Try invoking Netscape as netscape -ncol 64 & to limit its color map use.