Bug ID 1298029: DB_monitor may end the wrong processes

Last Modified: Dec 18, 2024

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

Known Affected Versions:
13.1.4.1, 13.1.5, 13.1.5.1, 14.1.5.4, 14.1.5.6, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1, 16.1.5

Opened: May 11, 2023

Severity: 2-Critical

Symptoms

If there are a lot of LTM or GTM database monitors in use, then the DB_monitor process may, in extremely rare circumstances, inadvertently end the processes that are not intended to be stopped.

Impact

Some linux processes may unexpectedly end.

Conditions

Many database monitors, frequent PID reuse. This should be extremely rare.

Workaround

Preiodically clean up with PID files: find /var/run/ -iname \*SQL__* -mtime +1 -exec rm -vf '{}' ';' and/or increase the number of available Linux PIDs: echo 4194304 > /proc/sys/kernel/pid_max

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips