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

Last Modified: Mar 01, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2

Fixed In:
15.1.0, 15.0.1.3, 14.1.2.3, 13.1.3.6, 12.1.5.3

Opened: Aug 14, 2019
Severity: 3-Major

Symptoms

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)

Impact

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

Conditions

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 775901.

Workaround

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 775901.

Behavior Change