IBM Support

Collecting Data: Available Logging for the FillDB server component

Technote (troubleshooting)


Problem(Abstract)

Various logs and traces useful for troubleshooting that can be enabled for the FillDB server component.

Resolving the problem

The following logs and traces can be enabled for the FillDB server component to capture debug information, analyze performance, and copy out files before they are processed and inserted into the database.

By default; in the installation, the following two settings are in place to enable basic critical FillDB logging messages (only startup and critical messages are logged by default):

Default FillDB Logging (enabled by default):
These settings are in place by default:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\FillDB
    Type: REG_SZ
    Name: DebugOut
    Value: C:\Program Files (x86)\BigFix Enterprise\BES Server\FillDBData\FillDB.log
    Type: REG_DWORD (32-bit)
    Name: EnableLogging
    Value: 1 (setting it to 0 turns off FillDB logging completely)

Additional logging can then be enabled:

Enable FillDB Debug Logging:
To enable debug logging, you will need to add the following registry settings with the following values:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\FillDB

Type: REG_SZ
Name: EnabledLogs
Value: critical;debug;database (setting it to nothing reverts back to the default where only critical messages are logged)


    * Requires a restart of the FillDB service
Enable FillDB Performance Logging:
To enable performance logging, you will need to add the following registry settings with the following values:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\FillDB


    Type: REG_SZ
    Name: PerformanceDataPath
    Value: C:\Program Files (x86)\BigFix Enterprise\BES Server\FillDBData\FillDBPerfLog.txt

    Note: The value for PerformanceDataPath needs to be set to a file name in a directory that exists.

    Type: REG_SZ
    Name: EnablePerformanceLogs
    Value: 1 (setting it to 0 deactivates it)

    * Requires a restart of the FillDB service

Enable FillDB Carbon Copy:
The carbon copy setting instructs the server to make copies of all the reports that are posted to the server before the FillDB process has put them into the database. These reports can then be analyzed to troubleshoot a variety of reporting issues that may be occurring in the deployment.

To enable the carbon copy feature, you will need to add the following registry setting with the following value:

HKLM\Software\BigFix\Enterprise Server\PostResults

    Note: The PostResults key does not exist by default and may need to be created first.

    Type: REG_SZ
    Name: CarbonCopyPath
    Value: C:\temp\reportcopies

    Note: The value for CarbonCopyPath needs to be set a directory that exists. For example reportcopies needs to exist at C:\temp. If it does not exist, please create it ahead of enabling the setting.

    Note: DO NOT enable the path to output the carbon copy reports back to anywhere within or under the BES Server directory as this would eventually cause a block to reporting and a reporting backlog for the FillDB service.

    * Requires a restart of the BES Root Server service
Enable Capture of Discarded Bad Reports:
HKLM\Software\BigFix\Enterprise Server\FillDB

    Type: REG_SZ
    Name: BadDocumentsPath
    Value: C:\temp\badreports

    Note: The value for BadDocumentPath needs to be set a directory that exists. For example badreports needs to exist at C:\temp. If it does not exist, please create it ahead of enabling the setting.

    Note: DO NOT enable the path to output the bad reports back to anywhere within or under the BES Server directory as this would eventually cause a block to reporting and a reporting backlog for the FillDB service.

    * Requires a restart of the FillDB service
Additional Available Tools:
  • FillDB Perflog Analyzer: is a tool that can be used to parse through the FillDB Performance Log and generate a more readable summary table from the performance information. Instructions and download link for the FillDB Perflog Analyzer can be found here.
  • The Decompress Utility: can be used to decompress reports captured from the Bad Reports capture process or on compressed reports copied directly out of the FillDB buffer dir.

Download the utility here.
    1. Create a folder and put decompress.exe in the folder.
    2. In the same folder create 2 sub folders, one called "Compressed" and one called "Decompressed"
    3. Take the discarded files (one at a time is easiest), and put it into the folder named "Compressed"
    4. Double click Decompress.exe.
    5. Open the Decompressed folder and it should contain both the compressed and decompressed version of the reports.

Related information

FillDB Perflog Analyzer
Decompress Utility

Document information

More support for: IBM BigFix family
Server

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1701916

Modified date: 01 November 2017


Translate this page: