Bug ID 710424: Possible SIGSEGV in GTMD when GTM persistence is enabled.

Last Modified: Jan 06, 2021

Bug Tracker

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

Known Affected Versions:
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, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5

Fixed In:
14.1.0, 14.0.0, 13.1.0.6, 12.1.3.4, 11.6.5.2

Opened: Mar 15, 2018
Severity: 2-Critical
Related AskF5 Article:
K00874337

Symptoms

When GTM persistence is enabled, GTMD may occasionally crash and restart. The gtmd process reports a SIGSEGV when persistence is enabled. As a result of this issue, you may encounter one or more of the following symptoms: -- The gtmd process reports a SIGSEGV and produces a core file. -- The gtmd process restarts, which prevents clients from receiving answers to requests.

Impact

The gtmd process may occasionally restart, which prevents clients from receiving answers to requests.

Conditions

This issue occurs when the following condition is met: Persistence is enabled for the wide IP pools.

Workaround

Disable persistence on wide IP pools.

Fix Information

The gtmd process no longer crashes and restarts when persistence is enabled.

Behavior Change