Principal trace log files

Table 3 contains locations, file names, and descriptions of trace logs that can help determine the source of problems with agents.

Table 3. Trace log files for troubleshooting agents

System where log is located	File name and path	Description
On the Tivoli Enterprise Monitoring Server	Windows: The file in the install_dir\InstallITM path UNIX: The candle_installation.log file in the install_dir/logs path	Provides details about products that are installed. Note: Trace logging is enabled by default. A configuration step is not required to enable this tracing.
	The Warehouse_Configuration.log file is in the following location on Windows systems: install_dir\InstallITM	Provides details about the configuration of data warehousing for historical reporting.
	The name of the RAS log file is as follows: Windows: install_dir\logs\ hostname_ms_timestamp-nn.log UNIX: install_dir/logs/ hostname_productcode_timestamp.log Note: File names for RAS1 logs include a hexadecimal time stamp. Also on UNIX, a log with a decimal time stamp is provided: `hostname_productcode_timestamp.log and hostname_productcode_ timestamp.pidnnnnn in the install_dir/`logs path, where nnnnn is the process ID number.	Traces activity on the monitoring server.
On the Tivoli Enterprise PortalServer	The name of the RAS log file is as follows: Windows: install_dir\logs\ hostname_cq_HEXtimestamp-nn.log UNIX: install_dir/logs/ hostname_cq_HEXtimestamp-nn.log Note: File names for RAS1 logs include a hexadecimal time stamp. Also on UNIX, a log with a decimal time stamp is provided:`hostname_productcode_timestamp.log and hostname_productcode_ timestamp.pidnnnnn in the install_dir/` logs path, where nnnnn is the process ID number.	Traces activity on the portal server.
	The teps_odbc.log file is located in the following path Windows: install_dir\InstallITM path UNIX: install_dir/logs	When you enable historical reporting, this log file traces the status of the warehouse proxy agent.
	The agent operations log files are as follows: instance_hostname_RJ.LG0 is the current log created when the agent was started instance_hostname_RJ.LG1 is the backup of the previous log These logs are in the following directory depending on the operating system that you are using: Windows: install_dir\tmaitm6\logs UNIX: install_dir/logs	Shows whether the agent was able to connect to the monitoring server. Shows which situations are started and stopped, and shows other events while the agent is running. A new version of this file is generated every time the agent is restarted. IBM Tivoli Monitoring generates one backup copy of the *.LG0 file with the tag .LG1. View .LG1 to learn the following details regarding the previous monitoring session: Status of connectivity with the monitoring server. Situations that were running. The success or failure status of Take Action commands.

Table 3. Trace log files for troubleshooting agents (continues)

System where log is located File name and path Description

On the Tivoli Enterprise PortalServer

System where log is located	File name and path	Description
On the Tivoli Enterprise PortalServer	The Take Action command log files are as follows: host_rj_takeactioncommand.log The logs are in the following directories: Windows: install_dir\tmaitm6\logs UNIX: install_dir/logs	Traces activity each time a Take Action command runs. For example, when a hypothetical start_command Take Action command runs, IBM Tivoli Monitoring generates a start_command.log file.
Definitions of variables: `timestamp` is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm `HEXtimestamp` is a hexadecimal representation of the time at which the process was started. `install_dir` represents the directory path where you installed the IBM Tivoli Monitoring component. `install_dir`can represent a path on the computer that host the monitoring system, the monitoring agent, or the portal. `instance` refers to the name of the database instance that you are monitoring. `hostname` refers to the name of the computer on which the IBM Tivoli Monitoring component runs. `nn` represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first is always retained, because it includes configuration parameters. `productcode` specifies the product codes, for example, um for Universal Agent or nt for Windows.

The Take Action command log files are as follows:

host_rj_takeactioncommand.log

The logs are in the following directories:

Windows: install_dir\tmaitm6\logs
UNIX: install_dir/logs

Traces activity each time a Take Action command runs. For example, when a hypothetical start_command Take Action command runs, IBM Tivoli Monitoring generates a start_command.log file.

Definitions of variables:

timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm

HEXtimestamp is a hexadecimal representation of the time at which the process was started.

install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dircan represent a path on the computer that host the monitoring system, the monitoring agent, or the portal.

instance refers to the name of the database instance that you are monitoring.

hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs.

nn represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first is always retained, because it includes configuration parameters.

productcode specifies the product codes, for example, um for Universal Agent or nt for Windows.

See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the complete set of trace logs that are maintained on the monitoring server.