Bug ID 905557: Logging up/down transition of DNS/GTM pool resource via HSL can trigger TMM failure

Last Modified: May 29, 2024

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

Known Affected Versions:
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, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1

Fixed In:
16.0.0, 15.1.2, 14.1.4, 13.1.5

Opened: May 01, 2020

Severity: 2-Critical

Symptoms

A TMM daemon logs a SIGSEGV error, halts, and then be restarted.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- A BIG-IP system configured to perform DNS/GTM Global Server Load Balancing. -- High Speed Logging (HSL) is configured. -- Multiple HSL destinations are configured. -- The enabled HSL settings include 'replication'. -- At least one HSL destination is up. -- At least one HSL destination is down. -- A pool resource changes state from up to down.

Workaround

Configure HSL with only a single log destination.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips