Bug ID 683061: Rapid creation/update/deletion of the same external datagroup may cause core

Last Modified: Apr 19, 2021

Bug Tracker

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

Known Affected Versions:
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, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 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, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4

Fixed In:
14.0.0

Opened: Sep 12, 2017
Severity: 3-Major

Symptoms

Notice and error messages and core when during rapid creation/update/deletion of the same external datagroup. -- notice tmm[15187]: 01010259:5: External Datagroup (/Common/Datagroup_1) queued. -- notice tmm[15187]: 01010259:5: External Datagroup (/Common/Datagroup_1) queued for update. -- err tmm[15187]: 01010258:3: External Datagroup (/Common/Datagroup_1) creation failed: initial load error, deleting.

Impact

TMM crashes and generates a core. Traffic disrupted while tmm restarts. Note: This is a timing-related crash that might not occur every time.

Conditions

Using an external datagroup, rapidly creating and updating, and then deleting it.

Workaround

Allow the tmm process enough time to finish processing external datagroup changes before starting another operation. Depending on the size of the datagroup, this might require from 1 second to 10 seconds or more. You can examine the LTM log for the create=finished message to help determine how much wait time is required.

Fix Information

None

Behavior Change