Bug ID 680804: TMM restart due to delayed keep alives

Last Modified: Jun 10, 2021

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,, 15.0.0, 15.0.1,,,,

Opened: Aug 29, 2017
Severity: 2-Critical


TMM killed with SIGABRT by the SOD process that monitors all process's health. TMM misses the keep alive, hence the restart. The stack trace shows that tmm was killed when it was waiting on a memory map (sys_mmap_obj) call.


Traffic disrupted while TMM restarts.


The memory map call is known to take a long time to complete when the disk IO sub-system is very slow. High IO can also be a result of memory starvation accompanied by intensive paging


This problem is not likely to persist after a TMM service restart. So no user intervention is required. If this problem happens repeatedly, it would be required to take a look at IO Resources in use at time of the database load or reload, and see if a way to lower IO can be found.

Fix Information


Behavior Change