Principal trace log files

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

Table 2. 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 Portal Server	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.
On the Tivoli Enterprise 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.
On the computer that hosts the monitoring agent	The RAS1 log files are as follows: Windows: hostname_p7_kp7agent _HEXtimestamp-nn.log in the install_dir\tmaitm6\logs directory UNIX: hostname_p7_HEXtimestamp-nn.log in the install_dir/logs directory These logs are in the following directories: Windows: `install_dir\tmaitm6\logs` UNIX: `install_dir/logs`	Traces activity of the monitoring agent.
	The agent operations log files are as follows: `instance_hostname_P7.LG0` is the current log created when the agent was started `instance_hostname_P7.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.
	The Take Action command log files are as follows: host_p7_instance_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.

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.

Examples: using trace logs

You can open trace logs in a text editor to learn some basic facts about your IBM Tivoli Monitoring environment. The following examples are from the Tivoli Enterprise Monitoring Server log.

Example one

This excerpt shows the typical log for a failed connection between a monitoring agent and a monitoring server with the host name server1a:

(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,
 "location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to
 broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable
 to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

Example two

The following excerpts from the trace log for the monitoring server show the status of an agent, identified here as "Remote node." The name of the computer where the agent is running is SERVER5B:

(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:P7 is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:P7 is OFF-LINE.

Key points regarding the preceding excerpt:

The monitoring server appends the P7 product code to the server name to form a unique name (SERVER5B:P7) for this instance of the Blue Medora Agent for Files and Directories. This unique name enables you to distinguish multiple monitoring products that might be running on SERVER5B.
The log shows when the agent started (ON-LINE) and later stopped (OFF-LINE) in the environment.
For the sake of brevity an ellipsis (...) represents the series of trace log entries that were generated while the agent was running.
Between the ON-LINE and OFF-LINE log entries, the agent was communicating with the monitoring server.
The ON-LINE and OFF-LINE log entries are always available in the trace log. All trace levels that are described in Setting RAS trace parameters provide these entries.

On Windows, you can use the following alternate method to view trace logs:

In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed.
Right-click a component and select Advanced > View Trace Log in the pop-up menu. For example, if you want to view the trace log of the Files and Directories agent, right-click the name of the that agent in the window. You can also use the viewer to access remote logs.
Note:

The viewer converts time stamps in the logs to a format that is easier to read.