Bug ID 569472: TMM segfault in lb_why_pmbr_str after GTM/BIG-IP DNS disables a GTM pool and LB why log is enabled

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.1 HF1, 11.5.4 HF2

Opened: Jan 22, 2016
Severity: 3-Major
Related AskF5 Article:
K91000137

Symptoms

tmm cores with sigsegv within lb_why_pmbr_str.

Impact

tmm cores.

Conditions

1. Disable a GTM/BIG-IP DNS pool or pool member; 2. pool-member-selection is enabled for load-balancing-decision-log-verbosity.

Workaround

Disable pool-member-selection for load-balancing-decision-log-verbosity.

Fix Information

tmm no longer cores when disabling pool-member-selection for load-balancing-decision-log-verbosity.

Behavior Change