Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0
12.1.0, 12.0.0 HF1, 11.6.1, 11.5.4, 11.4.1 HF10
Opened: Sep 09, 2015
Related AskF5 Article: K17322
TMM crash and coredump while logging to remote logging server when an HA failover occurs.
TMM runs out of stack and dumps core. Stack trace shows recursion in errdefs. The system cannot function under these conditions. This is an issue that might occur anytime logs are generated when managing resources that are also used by the logging system itself.
The problem might occur when: 1. A log message is created as the result of errors that can occur during log-connection establishment. 2. An error occurs while attempting to connect to the remote logging server. 3. The Primary HA member fails over. The crash occurs on the HA member which was the Primary member prior to the failover.
Two possible workarounds are available: 1) Create a log filter specifically for message-id :1010235: that either discards or directs such messages to local syslogs. 2) If the problem occurs on TMM startup, disable and then re-enable the corresponding log source once the TMM starts up.
Logging recursion no longer occurs in TMM during failover while the system is attempting to connect to the remote logging server.