Bug ID 591124: gtmd core while adding a new GTM to an existing sync group.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6

Fixed In:

Opened: May 04, 2016

Severity: 2-Critical

Related Article: K30640422


While adding a new GTM to an existing sync group, the new system's configuration conflicts with configurations on the other GTM systems in the sync group and causes gtmd to core on the unit being added.


New GTM unit being added generated a gtmd core file. Configs on other production GTM devices in the network might also be compromised, and might need to be restored from backup. The system might produce a core dump at the moment of sync group corruption.


Adding a new GTM to sync group. Other, more specific conditions are not known. That makes this rarely encountered, intermittent issue difficult to predict and reproduce.



Fix Information

Although the exact cause is unknown, the gtmd process has been modified to more gracefully handle the condition that generated the gtmd core while adding a new GTM to an existing sync group.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips