This page lists the log and debug files for the various Tivoli Endpoint Manager (TEM) components.



Agents

Generated in the following locations for the respective OS, the TEM Agent logs have a built-in rotation scheme to keep 10 days (configurable) of logs capped at a max size (configurable):

  • Windows: C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\Logs
  • Unix/Linux: /var/opt/BESClient/__BESData/__Global/Logs
  • Mac: /Library/Application Support/Bigfix/BES Agent/__BESData/__Global/Logs
 
TEM Agents have a verbose debug log known as the "emsg log" that can be enabled for troubleshooting purposes.
More information about agent logs at: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Agent%20Logs

 

Console

  • The Console does not write a log by default.
  • A debug log can be enabled for troubleshooting by adding the registry keys:
    • HKCU\Software\BigFix\Enterprise Console
    • "debugout" = "c:\console.log"
    • "enabledlogs" = "all"



Server

FillDB

  • FillDB Debug Log -- Used to troubleshoot issues with agent reports or FillDB connection errors. By default, log will show "critical" log messages
    • Default location: "FillDBData" folder of the TEM Server (e.g., "C:\program files\BigFix Enterprise\BES Server\FillDBData\FillDB.log")
    • Log controlled by registry key
      • HKLM\Software\BigFix\Enterprise Server\FillDB
      • "EnabledLogs"
        • default: "critical"
        • add: "critical;debug" to get additional debug logging




  • FillDB Performance Log -- Used to measure and troubleshoot FillDB performance issues with the server/database
  • Disabled by default
  • Log controlled by registry key:
    • HKLM\Software\BigFix\Enterprise Server\FillDB
    • "PerformanceDataPath"
    • Example: "C:\program files\BigFix Enterprise\BES Server\FillDBData\FillDBPerf.log"
  • Requires FillDB service restart after registry key change to activate.





     

Web Reports

  • Web Reports logs -- Used to troubleshoot web reports issues
  • HKLM\Software\BigFix\Enterprise Server\BESReports
  • "LogOn" (dword)
    • 0 for log off, 1 for on
  • "EnabledLogs" (string)
    • "critical;debug;memory;performance;timing"
  • "LogPath" (string)
    • full path to log file (i.e. "C:\program files\BigFix Enterprise\BES Server\WR.log")
  • "Debug" (string)
  • "1" will display more detail for errors inside the web reports user interface.





     

Relay/Root Server

  • Relay Log -- This log contains information on the web server component of the relay, along with debugging information for top level exceptions on any of the debugging threads. Default enabled in non-verbose mode named "BESRelay.log" on root server ("C:\program files\BigFix Enterprise\BES Server\BESRelay.log") and Relays ("C:\program files\BigFix Enterprise\BES Relay\logfile.txt").
    • To enable Verbose flag, enable a client setting "_BESRelay_Log_Verbose"="1" on the Server or any Relay. (Warning, this is an incredibly verbose log and includes information for every single incoming connection, along with performance measuring information.