Bug ID 945925: tmm could be stuck in a restart loop when remote logging to a fqdn destination is configured

Last Modified: Apr 11, 2023

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 16.0.0,, 16.0.1,

Fixed In:
16.1.0,, 15.1.4,

Opened: Sep 16, 2020

Severity: 2-Critical


- TMM is stuck restarting on a BIG-IP device or VE instance - Unable to process application traffic - /var/log/tmm logfile may contain the notice "MCP connection aborted, exiting"


- Unable to process application traffic since the required component cannot be brought up


- Remote logging destination is configured (System-Logs-Configuration-Remote logging) and pointing to a FQDN hostname - FQDN hostname temporarily or permanently fails to resolve (e.g. DNS failure or congestion) - Reboot or upgrade of a BIG-IP instance or other conditions leading to tmm restart


- Perform audit of DNS server(s), make sure FQDN destination resolves successfully, OR - Use IP address as remote logging destination, OR - Disable remote logging feature

Fix Information

no fix yet

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips