Bug ID 857845: TMM crashes when 'server drained' or 'client drained' errors are triggered via an iRule

Last Modified: Oct 16, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1

Fixed In:
16.0.0, 15.1.2,,

Opened: Dec 04, 2019

Severity: 3-Major


Whenever the server or client side data have not been drained, 'server drained' or 'client drained' appear in /var/log/tmm as errors.


TMM crashes and can cause an outage on standalone system or failover in a DSC. Traffic disrupted while tmm restarts.


-- Using iRule configuration with LB::detach or LB::connect. -- Server- or client-side data has not been drained before those statements are triggered.



Fix Information

TMM no longer crashes and the 'server not drained' or 'client not drained' message is logged instead. If tmm.oops is set to 'log', the OOPS messages is reported in /var/log/tmm.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips