Working with logs
The following topics provide the names and descriptions of the basic log files generated by Gateway Server, outlines which files are useful for solving specific problems, and gives instructions on how they can be viewed using the OSR utility:
Basic log files
The following table lists the names and descriptions of some of the basic Gateway Server log files. Most of the files are not installed with the application. They are created after you use Gateway Server for a period of time. The content of these files might be useful in solving issues. The majority of the log files are stored in the following directory:
- On Windows: %BEST1_COLLECT_HOME%\bgs\log
- On UNIX: $BEST1_HOME/bgs/log
Log files that are not stored in the above location are noted.
Basic Gateway Server log files
The last four digits in the file name represent the port number. 6767 is the default port number. This file also has a backup copy of the same name, with a .bak extension. The header in this file shows you:
This file contains the errors that the Manager daemon detects. It also has a backup copy of the same name, with a .bak extension.
The agent startup file initiates first. It tries to start an agent on the default port, unless another port is specified. This file checks to make sure that another agent is not currently running on the port specified (the default, if not specified). If an agent is running, a message is sent to the agent and the agent stops. This file also has a backup copy of the same name, with a .bak extension.
A text file of the alerts that agents have reported to the console. It includes alerts that were asserted as well as those which were activated for each alert in each policy activated. This file is backed up every 600 messages. The backup files are named b1monitor.log_n, where n is a digit from 1 to 6.
Collect error log file. This file details what the collector is doing. It displays which metric groups are going to be collected and which are not supported. It also has a backup copy of the same name, with a .bak extension.
Contains information that best1collect receives from the service daemon. Usually this information records the time when the service daemon sends a collect request to best1collect.
This file contains the errors associated with the Investigate component. It also has a backup copy of the same name, with a .bak extension.
This is a text file of activity of the MRconsumer API. It also has a backup copy of the same name, with a .bak extension.
This is the service daemon error log file. It also has a backup copy of the same name, with a .bak extension. This file contains communication information between the service daemon and the agents on console and agent computers:
This is the log file for the OSR utility. It is stored in the OSR output directory, defined in osrlogfiles.cfg.
Matching log files to specific problems
The following table outlines which log files are useful for specific situations on both Windows and UNIX systems. These log files can be pulled from the agent node to the console node using bgsagent_logs.
All paths begin from the product install directory. For UNIX, $BEST1_HOME, and for Windows, %BEST1_COLLECT_HOME%.
List of useful log files for problem solving
For problems with
Refer to these files
Installation failing or the product cannot be started after the install
Data collection on a remote node
Data transfer from remote node to console
On UNIX remote node running:
On Windows remote node:
To debug this issue, you would also need the entire contents of the .../local/manager directory (for a UNIX console) or the entire contents of the ...\local\manager directory (for a Windows console).
On the UNIX remote node:
On the Windows remote node:
On the UNIX console:
On the Windows console:
UNIX console: The following files in the Manager Output directory:
UNIX Managing Node: