By default, logging and tracing is set to DEBUG_MIN. Higher levels give you
more detailed information about the installation process. This can be useful for
investigating any problems or errors that occur.
Level name
What is logged or traced
DEBUG_MIN
Most important method entries, exits and trace messages are
traced
DEBUG_MID
Most of the method entries, exits and trace messages are traced
DEBUG_MAX
All of the method entries, exits and trace messages are traced
You can set the level of logging and tracing by using the
/z
flag when you execute
the
setup.exe
file in the CLI.
v
For GUI installation use one of the following commands:
–
setup.exe /zDEBUG_MAX
–
setup.exe /zDEBUG_MID
–
setup.exe /zDEBUG_MIN
v
For silent installation use one of the following commands:
–
start /wait setup /z"DEBUG_MAX/sfC:\temp\SILENT_SERVER.txt" /s
/f2"C:\temp\silent_setup.log"
–
start /wait setup /z"DEBUG_MID/sfC:\temp\SILENT_SERVER.txt" /s
/f2"C:\temp\silent_setup.log"
–
start /wait setup /z"DEBUG_MIN/sfC:\temp\SILENT_SERVER.txt" /s
/f2"C:\temp\silent_setup.log"
UNIX installer and configuration logs
Obtain details about the installation (or upgrade) process in the logging and
tracing information. You can set the trace levels.
For tracing and logging Java code (that is run on UNIX systems), this mechanism
enables problem debugging. Two sets of information are created – logs and traces.
Logs (*.log) are globalized and traces (*.trc) are in English. They contain entry and
exit parameters of method and stack traces for exceptions. The amount of
information traced depends on the level of tracing set.
Level name
What is logged or traced
LOG_ERR
Only exceptions and errors are logged and
traced
LOG_INFO
Also log messages are logged and traced -
DEFAULT
DEBUG_MIN
Also most important method entries, exits
and trace messages are traced
DEBUG_MID
Most of the method entries, exits and trace
messages are traced
DEBUG_MAX
All of the method entries, exits and trace
messages are traced
The level can be set in configuration files or by exporting an environment variable
called TRACE_LEVEL with one of the values mentioned above. Configuration of
RAS settings is stored in the following files:
v
CH/config/ITMInstallRAS.properties
(for installation)
40
IBM Tivoli Monitoring: Troubleshooting Guide
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...