Bug ID 814761: PostgreSQL monitor fails on second ping with count != 1

Last Modified: Sep 13, 2023

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

Known Affected Versions:

Fixed In:

Opened: Aug 14, 2019

Severity: 3-Major


When using one of the DB monitors (Oracle, MSSQL, MySQL, PostgreSQL) to monitor the health of a server, the pool member may initially be marked UP, but then will be marked DOWN on the next and all subsequent pings. When this occurs, an error message similar to the following appears in the monitor-instance log under /var/log/monitors: Database down, see /var/log/DBDaemon.log for details. Exception in thread "DBPinger-##" java.lang.AbstractMethodError: org.postgresql.jdbc3.Jdbc3Connection.isValid(I)Z at com.f5.eav.DB_Pinger.db_Connect(DBDaemon.java:1474) at com.f5.eav.DB_Pinger.db_Ping(DBDaemon.java:1428) at com.f5.eav.MonitorWorker.run(DBDaemon.java:772) at java.lang.Thread.run(Thread.java:748)


Unable to monitor the health of postgresql server pool members accurately.


This may occur if all of the following conditions are true: 1. You are using a DB monitor (Oracle, MSSQL, MySQL, PostgreSQL) configured with a 'count' value of either '0' or a value of '2' or higher. 2. You are using a version of BIG-IP (including an Engineering Hotfix) which contains the fix for ID 769309.


To work around this issue, configure a 'count' value of '1' in the postgresql monitor configuration.

Fix Information

The DB monitor reports the health of a DB server pool member accurately in conjunction with the fix for ID 769309.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips