Bug ID 475495: SQL monitor enhancements

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
10.2.4

Fixed In:
10.2.4 HF12

Opened: Aug 13, 2014
Severity: 3-Major
Related AskF5 Article:
K57250454

Symptoms

SQL (MSSQL, MySQL, Oracle, Postgres) monitors may occasionally hang for unknown reasons.

Impact

MSSQL, MySQL, Oracle, Postgres monitors may occasionally hang.

Conditions

This occurs when using MSSQL, MySQL, Oracle, and Postgres monitors.

Workaround

None.

Fix Information

Many small minor fixes have been made which mitigate the situations where the problem has been reproducible. In addition, two debugging aids have been added: 1. Logging has been significantly enhanced. 2. A new command has been added to help diagnose the state of the SQL monitors: /usr/share/monitors/DB_monitor cmd status [RD] [debug] RD: optional, the route domain for the desired Java daemon (each route domain gets a separate daemon). debug: optional, do debug logging. Examples: -- /usr/share/monitors/DB_monitor cmd status. -- /usr/share/monitors/DB_monitor cmd status 0. -- /usr/share/monitors/DB_monitor cmd status 17. -- /usr/share/monitors/DB_monitor cmd status 9 debug.

Behavior Change

Addition of "cmd status" debugging command.