Solstice SyMON 1.6 User's Guide
この本のみを検索
PDF 文書ファイルをダウンロードする
CHAPTER 6

Troubleshooting


This chapter presents troubleshooting tips for Solstice SyMON.

Troubleshooting Tips

TABLE 6-1 presents troubleshooting problems and the suggested corrective actions.
TABLE 6-1
ProblemSystem DisplayCorrective 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 CD-ROM (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 Sun 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)
ProblemSystem DisplayCorrective 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 requires
CDE 1.0.1 and later
versions.
"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 Create New or Modified Rules" on page 98 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 for an older release of Solstice SyMON. Install the SUNWsyrt package for this release of Solstice SyMON (see Chapter 2).
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 for an older Solstice SyMON release and install the SUNWsyu package for this version of Solstice SyMON (see Chapter 2).
TABLE 6-1 (Continued)
ProblemSystem DisplayCorrective Action
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 for an older Solstice SyMON release and install the SUNWsys or SUNWsye packages, respectively for this release of Solstice SyMON (see Chapter 2).
A Solstice SyMON client not running this version of Solstice SyMON is attempting to monitor a host running this version of Solstice SyMON.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 this release of Solstice SyMON (see Chapter 2).
TABLE 6-1 (Continued)
ProblemSystem DisplayCorrective 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.6 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 this release of Solstice SyMON (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 the current version.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.6>.

Upgrade the agent host to this Solstice SyMON release (see Chapter 2).
Log Scanner remains yellow or red.Start the GUI after the agents are started or restart the GUI after the Log Scanner remains yellow or red.