This documentation supports releases of BMC Helix Continuous Optimization up to December 31, 2021. To view the latest version, select the version from the Product version menu.

Working with the Gateway Server logs

You can use the Gateway Server log files to troubleshoot issues. You can view these files by using the OSR utility.

To retrieve log files from remote computers

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:

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 when you use the Gateway Server for some time: $BEST1_HOME/bgs/

You can use these files to solve specific issues.


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 start-up process. The log file is: nodeName-bgsSD.log

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*