Page tree

Skip to end of metadata
Go to start of metadata

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

File name

Description

nodeName-bgsagent_6767.log

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:

  • Which port number the agent is using
  • Which port number the manager daemon is using
  • Who started the agent
  • What computer the agent is running on
  • It might also provide information about the repository.cfg file or the .als file.

nodeName-b1mgrdmonErrors.log

This file contains the errors that the Manager daemon detects. It also has a backup copy of the same name, with a .bak extension.

nodeName-bgsagentstartup.log

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.

nodeName-b1monitor.log

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.

nodeName-bgscollect-noInstance.log

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.

nodeName-best1collect_SD.log

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.

nodeName-bgsmonitorErrors.log

This file contains the errors associated with the Investigate component. It also has a backup copy of the same name, with a .bak extension.

nodeName-mrconsumer.log

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.

nodename-bgsSD.log

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, including the following information related to proxy discovery:

  • If using an agentless computers list
  • The number of nodes specified for each domain or if the domain is set to unlimited
  • The status of the node discovery and validation processes

OSR-hostName-indexNumber.olog

This is the log file for the OSR utility. It is stored in the OSR output directory, defined in osrlogfiles.cfg (see, OSR configuration files).

OSR uses a segmented log file system. After the log file reaches a certain size, OSR stops writing to it and creates a new file with a higher index number. In addition, OSR maintains a limit on the number of segments allowed.

Note: Earlier versions of OSR used the following format for naming files mmm_dd_yyyy.hh.mm.ss_osr.log.

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

On UNIX:

  • The installation logs created in the /var/tmp or /tmp directory.
  • The installDir/Gateway_Server_install_log.txt log. This log is created by the b1config7510.shscript and will contain errors about the configuration stage of the installation. This log exists only if the install said it completed successfully but the product still does not work.

On Windows:

  • %TEMP%\Gateway_Server_install_log.txt

Data collection on a remote node

On UNIX:

  • .../bgs/log/nodeName-bgscollect-noInstance.log
  • .../bgs/log/nodeName-bgsagent_6767.log
  • .../bgs/log/nodeName-bgsSD.log

On Windows:

  • ...\bgs\log\nodeName-bgscollect-noInstance.log
  • ...\bgs\log\nodeName-bgsagent_6767.log
  • ...\bgs\log\nodeName-bgsSD.log

Data transfer from remote node to console

On UNIX remote node running:

  • .../bgs/log/nodeName-bgsagent_6767.log
  • .../bgs/log/nodeName-bgsSD.log

On Windows remote node:

  • ...\bgs\log\nodeName-bgsagent_6767.log
  • ...\bgs\log\nodeName-bgsSD.log

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).

Service Daemon

On the UNIX remote node:

  • .../bgs/log/nodeName-bgsagent_6767.log
  • .../bgs/log/nodeName-bgsSD.log

On the Windows remote node:

  • ...\bgs\log\nodeName-bgsagent_6767.log
  • ...\bgs\log\nodeName-bgsSD.log

On the UNIX console:

  • .../bgs/monitor/nodeName-best1collect_SD.log

On the Windows console:

  • ...\bgs\monitor\nodeName-best1collect_SD.log

Manager

UNIX console: The following files in the Manager Output directory:

  • date-date.ProcessDay.out log file.
  • date-date.Variables file

Windows console:

  • Any files in your Manager Output directory created for that day.

Analyze

UNIX Managing Node:

  • Analyze commands file (.an file)
  • Analyze log file (.anlog) which resides in the same directory as the .an file
  • A core file (if one exists)

Windows console:

  • Analyze commands file (.an file)
  • Analyze log file (.anlog) which resides in the same directory as the .an file
  • DrWatsn32.log file if Analyze is terminating with a Dr. Watson error

Investigate

UNIX console:

  • .../bgs/monitor/nodeName-b1monitor.log
  • .../bgs/monitor/nodeName-bgsmonitorErrors.log
  • .../bgs/monitor/nodeName-b1mgrdmonErrors.log

Windows console:

  • ...\bgs\log-best1monitor_si.log
  • ...\bgs\log-BMCChartOCX.log
  • ...\bgs\log-DrillDown.log