Working with the Gateway Server logs

You can use the Gateway Server log files to troubleshoot issues.

Retrieving log files

Use the bgsagent_logs command line utility to retrieve the Gateway Server log files from a remote Agent computer without logging on to the computer. 

For example, use the following command to retrieve the Agent and Collector log files:

$BEST1_HOME/bgs/bin/bgsagent_logs -n agentNode

where agentNode is the name of the Agent computer from which you want to retrieve and display the log files.

Gateway Server log files

The following table describes some of the Gateway Server log files. Most of the files are not installed with the application. They are created in the following directory after you use the Gateway Server for some time: $BEST1_HOME/bgs/log/

You can use these files to solve specific issues.


File name

Description

nodeName-bgsagent_6767.log

The last four digits in the file name represent the port number. The default port number is 6767. This file also has a backup copy with the same name and .bak extension. The header in this file displays the following information:

  • Port number the Agent is using
  • Port number the manager daemon is using
  • The user who started the Agent
  • The computer where the Agent is running
  • 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 with the same name and .bak extension.

nodeName-bgsagentstartup.log

The Agent startup file. It is used to start an Agent on the default port unless another port is specified. The file checks whether another Agent is currently running on the specified port (the default, if not specified). If the Agent is running, a message is sent to stop the Agent. This file also has a backup copy with the same name and .bak extension.

nodeName-b1monitor.log

A text file of the alerts that the Agents have reported to the console. It includes alerts that were asserted and those which were activated for each alert in each activated policy. A backup of this file is created after every 600 messages. The backup files are named b1monitor.log_n, where n is a digit from 1 to 6.

nodeName-bgscollect-noInstance.log

This file provides the status of the collector. It displays the metric groups that will be collected and those that are not supported. This file also has a backup copy with the same name and .bak extension.

nodeName-best1collect_SD.log

This file includes the time when the service daemon sends a collect request to best1collect.

nodename-bgsSD.log

This service daemon error file contains the following details:

  • The number of nodes specified for each domain
  • The status of the node discovery and validation processes

OSR-hostName-indexNumber.olog

This log file for the OSR utility is stored in the OSR output directory as defined in osrlogfiles.cfg.
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. Also, OSR maintains a limit on the number of allowed segments.
Earlier versions of OSR used the following format for naming files: mmm_dd_yyyy.hh.mm.ss_osr.log.

Log files categorized by problem area

The following table lists which log files are useful for specific situations on UNIX systems. These log files can be retrieved from the Agent node to the console node by using bgsagent_logs.

All paths begin from the product installation directory. For UNIX, it is $BEST1_HOME.

For problems with

Refer to these files

Installation failure or the product not starting after installation

  • 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.sh script and contains errors about the configuration stage of installation. The log is created only when the installation is completed successfully but the product still does not work.

Data collection on a remote node

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

Data transfer from a remote node to the console

On UNIX remote node running:

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

To debug this issue, you need the entire contents of the .../local/manager directory.

Service daemon

On the UNIX remote node:

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

On the UNIX 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

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)

Investigate

UNIX console:

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

Service daemon and the bgsSD log file

The service daemon resides on the remote node and it dynamically starts the Agent.

  • On Windows, the service daemon is located at this path: %BEST1_COLLECT_HOME%\bgs\bin.
  • On UNIX, the service daemon is located at this path:  /etc/bgs/SD
    When the installation script runs, it creates the Service Daemon directory and creates a link to the service daemon executable (bgssd) in this directory. (The option to change this directory is available during installation.)

The service daemon also creates a very small log file as a part of the Agent startup process. The log file is: nodeName-bgsSD.log

Was this page helpful? Yes No Submitting... Thank you

Comments