Bug ID 2033781: Memory allocation failed: can't allocate memory to extend db size

Last Modified: Aug 15, 2025

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.5.0, 17.5.1

Opened: Aug 14, 2025

Severity: 3-Major

Symptoms

When tmm cannot expand the eXtremeDB database, it logs an error in /var/log/tmm: err tmm1[21087]: 01010004:3: Memory allocation failed: can't allocate memory to extend db size

Impact

Tmm does not crash but the eXtremeDB state is inconsistent with other tmms and could lead to unpredictable behavior such as virtual servers not working, iRules failing to work, bot defense failing to work

Conditions

-- BIG-IP in operation -- A configuration change is made that causes tmm to allocate more memory to eXtremeDB. Examples include: - Adding a clientssl or serverssl profile - Modifying a datagroup - A bot defense sync occurs

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips