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

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

 

 

 

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

BMC Helix Capacity Optimization 19.11