IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей, Страница: 92 / 310

Many files in the First Failure Data Capture log directory
On Windows systems, there are eWAS logs in the following location of the IBM
Tivoli Monitoring home directory:
CANDLE_HOME\CNPSJ\profiles\ITMProfile\logs\ffdc\
And, on UNIX systems, they are found in the following directory:
CANDLE_HOME/arch/iw/profiles/ITMProfile/logs/ffdc/
These log files might contain the following exceptions:
org.omg.CORBA.BAD_OPERATION
CORBA.TRANSIENT
ClassNotFound on MQJMS
These exceptions can be ignored and have no impact on either eWAS or IBM Tivoli
Monitoring functionality.
Monitoring agents fail to start after agent support or
multi-instance agents are installed
Monitoring agents on an IBM Tivoli Monitoring V6.2.1 (or later) managed system
that have an unsupported system GSKit version installed might fail to start after
an IBM Tivoli Monitoring V6.2 Multi-Instance Agent or IBM Tivoli Monitoring V6.2
Agent Support is locally installed.
The installer used by both IBM Tivoli Monitoring V6.2 Multi-Instance Agents
(including fix packs) and IBM Tivoli Monitoring V6.2 Application Support causes
monitoring agents on an IBM Tivoli Monitoring V6.2.1 managed system (or later)
to revert back to using the system GSKit instead of the IBM Tivoli Monitoring
embedded GSKit. This issue occurs on local installations only. Remote installation
(remote deploy) does not have this issue.
If a system GSKit is installed on the managed system at a level supported by IBM
Tivoli Monitoring, the monitoring agents continue to operate normally.
Monitoring agents might fail to start, however, if all of the following conditions are
met:
v
The managed system does not have a system GSKit installed or the system
GSKit is at a version not supported by IBM Tivoli Monitoring V6.2.1 or later.
v
The agent is configured to use secure communications (IP.SPIPE) rather than
normal communication (IP.PIPE).
If agents on a managed system fail to start after an IBM Tivoli Monitoring V6.2
Multi-Instance Agent or IBM Tivoli Monitoring V6.2 Agent Support is installed,
any one of the following corrective actions can be taken:
v Run kinconfig.exe -G on the managed system.
v
OR
v Reconfigure any of the IBM Tivoli Monitoring V6.2.1 (or later) monitoring agents
on the managed system by running
kinconfig.exe -rKproductcode
.
v
OR
v
Install another IBM Tivoli Monitoring V6.2.1 monitoring agent (or later).
74
IBM Tivoli Monitoring: Troubleshooting Guide