Bug ID 1388621: Database monitor with no password marks pool member down

Last Modified: Jun 21, 2024

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 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,, 15.1.10,,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,, 17.1.0,,,, 17.1.1,,,

Opened: Oct 25, 2023

Severity: 3-Major


If an LTM or GTM database monitor is configured with a username to log in to the database, but without a password, pool members monitored by that monitor will be marked Down. When this issue occurs, an error message similar to the following (for a postgresql monitor in this example) will appear in the DBDaemon log file (/var/log/DBDaemon-*.log): [MonitorWorker-###] - incomplete parameters: m_connectStr:'jdbc:postgresql://###.###.###.###:##/postgres' m_user:'*********' m_password:'null' max_use:'#' m_inst_id:'******' The "incomplete parameters" and "m_password:'null'" items are the relevant parts of this error message.


Pool members monitored by a database monitor, the configured will be marked Down.


This may occur under the following conditions: -- LTM or GTM pool members are configured to use a database monitor, such as: -- mssql -- mysql -- oracle -- postgresql -- The monitor is configured with a username, but no password -- And this configuration is otherwise valid: The username is a configured in the target database with no password, and no password is required by the database for authentication of that user. -- The version of BIG-IP, or BIG-IP Engineering Hotfix, which includes a fix for Bug ID1025089.


Following is workaround for this issue: -- Configure the database user with a password, and require password authentication for the user -- Configure the database monitor with the correct password for the configured username

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips