Enabling debug/verbose logging for the BES Root Server and BES Relay services

This procedure describes the steps to enable debug/verbose logging on the BigFix Server or Relays, to log the activity performed by the BigFix Server and by the Relays.

Perform the following steps to enable debug/verbose logging level on BigFix server or relay.

The logging can be enabled by different means; using a Fixlet, creating a BigFix client setting with the BigFix Console or enabling it manually on the machine.

Enabling logging through the Fixlets

Use the following BESSupport Fixlets to enable/disable verbose logging on the BigFix server or relay:
  • Fixlet ID: 4595 - Enable Server verbose log
  • Fixlet ID: 4596 - WARNING: Server verbose log is enabled
  • Fixlet ID: 4776 - Enable Relay verbose log
  • Fixlet ID: 4777 - WARNING: Relay verbose log is enabled

Enabling logging through the BigFix Console

  1. Log in to the console as a master console operator.
  2. Right click the BigFix Server or relay computer in the console.
  3. Select Edit Computer Settings....
  4. Check in the list to see if the _BESRelay_Log_Verbose setting has already been created. If it has, click the button Edit and change its value to 1 (to enable it).
  5. If the setting has not been created, click the button Add to create it. Enter _BESRelay_Log_Verbose for the setting name and 1 for the setting value to enable the verbose logging.


  6. Click OK. An action named "Change '_BESRelay_Log_Verbose' Setting" is taken targeted at the BigFix server or relay machine.
  7. After the action has completed successfully (and the setting has been applied), the new logging level is effective for the BES Root Server service, while the restart of the BES Relay service is needed for BigFix relay. You can take action on Task # 447: Restart Service in the BES Support site to do this.

Enabling logging manually through the registry (Windows)

  1. Log in to the BigFix server or relay machine.
  2. Open up the registry editor (regedit).
  3. Add the registry key _BESRelay_Log_Verbose in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\EnterpriseClient\Settings\Client.
  4. Create a REG_SZ value named "value".
  5. Set the value to 1.


  6. Restart the BES Relay service if on a relay, while it is not needed on the BigFix Server.

Verbose data is output to <BigFix_Server_Installation_Folder>\BESRelay.log file on the server and <BigFix_Relay_Installation_Folder>\logfile.txt on a relay.

An example of <BigFix_Server_Installation_Folder> on the server is C:\Program Files (x86)\BigFix Enterprise\BES Server.

Enabling logging manually through the settings file (Linux)

  1. Log in to the BigFix relay machine.
  2. Stop BESClient service, to prevent the changes to the configuration file are overwritten, with the command:
    service besclient stop
  3. Edit the configuration file /var/opt/BESClient/besclient.config and add or modify the following lines:
    [Software\BigFix\EnterpriseClient\Settings\Client\_BESRelay_Log_Verbose]
    effective date = [Enter Current Date Time In Standard Format]
    value = 1
    The effective current date time must be in a format similar to "Wed, 06 Jun 2012 11:00:00 -0700".
  4. Start BESClient service with the command:
    service besclient start
  5. Restart the BESRelay service if on a relay:
    service besrelay stop
    service besrelay start
Note: The restart of BESRootServer service for the BigFix Server is not required to make the change effective.
Note: Verbose data is output to the /var/log/BESRelay.log file on both the server and a relay.
Note: To disable verbose logging, set the BigFix Client setting to 0.

Warning: Leave the verbose logging on just the time needed to troubleshoot the issue you are experiencing, in order to save disk space and processing resources. In large environments, leaving verbose logging on for extended periods of time may heavily lower the BES root service performances causing console timeouts and server activities deadlocks.

Note: A maximum of 10 rotated log files will be maintained in addition to the active log file with the names logfile.txt, logfile.txt_0, logfile.txt_1, ..., logfile.txt_9. The default value is 50*1024*1024 (52,428,800) bytes.