Bug ID 851121: Database monitor DBDaemon debug logging not enabled consistently

Last Modified: Feb 14, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,

Fixed In:
17.1.1, 16.1.4, 15.1.10

Opened: Nov 19, 2019

Severity: 3-Major


Debug logging in the database monitor daemon (DBDaemon) for database health monitors (Microsoft SQL, MySQL, PostgreSQL, Oracle) is enabled on a per-monitor basis. When a ping is initiated for a particular monitor with debug logging enabled in the monitor configuration, debug logging in DBDaemon is enabled. When a ping is initiated for a particular monitor with debug logging disabled in the monitor configuration, debug logging in DBDaemon is disabled. When monitoring database pool members with a mix of monitors with debug logging enabled versus disabled, the result can be that debug logging in DBDaemon is enabled and disabled at times which do not correspond to all actions related to a specific database monitor, or pool members monitored by that monitor. In addition, debug messages logging internal DBDaemon state related to the management of the full collection of monitored objects, active threads, and other may not be logged consistently.


Logging of database monitor activities by DBDaemon may be inconsistent and incomplete, impeding efforts to diagnose issues related to database health monitors.


-- Using multiple database health monitors (Microsoft SQL, MySQL, PostgreSQL, Oracle). -- Enabling debug logging on one or more database health monitors, but not all. Debug logging for database health monitors is enabled by configuring the "debug" property of the monitor with a value of "yes". Debug logging is disabled by configuring the "debug" property with a value of "no" (default). # tmsh list ltm monitor mysql mysql_example debug ltm monitor mysql mysql_example { debug yes }


When attempting to diagnose database health monitor issues with DBDaemon debug logging, enable debug logging for ALL database monitors currently in use. Once diagnostic data collection is completed, disable debug logging for all database monitors currently configured/in use.

Fix Information

DBDaemon debug logging can now be enabled globally to facilitate diagnosing database health monitor issues. DBDaemon debug logging can be enabled globally by creating the following touch file: -- /var/run/DBDaemon.debug DBDaemon global debug logging can be disabled by removing or unlinking the above touch file. Creating or removing the above touch file has immediate effect. This mechanism enables/disables DBDaemon debug logging globally for all instances of DBDaemon which may be running under different route domains. In addition, when debug logging is enabled for a specific database monitor (Microsoft SQL, MySQL, PostgreSQL, Oracle), DBDaemon accurately logs all events for that monitor. The per-monitor debug logging is enabled independent of the global DBDaemon debug logging status. The timestamps in DBDaemon logs (/var/log/DBDaemon-*.log*) are now written using the local timezone configured for the BIG-IP system.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips