GTM emerg logger: Re-starting tmm1

it seems like a known issue, did you try this? http://support.f5.com/kb/en-us/solutions/public/12000/500/sol12547

it seems like a known issue, did you try this? http://support.f5.com/kb/en-us/solutions/public/12000/500/sol12547

Which version of TMM are you using? one KB points out that they fixed in 11.5 .... http://support.f5.com/kb/en-us/solutions/public/14000/900/sol14995.html

We get same error after 11.5.1 HF6 upgrade. Since version 11.5.1 Hf5 not this kind problem. So 11.5.1 HF6 we got After the reboot it started to send the message "emerg logger: Re-starting tmm1 After the reboot it started to send the message "emerg logger: Re-starting tmm And device not join to HA cluster. Not yet know, why this come on this H6 release?

I've also seen this on 11.5.1 HF6 and we weren't seeing it on HF4

Have you found a solution? I'm investigating it now.

Same symptoms, won't connect to the cluster, mostly saying disconnected but very intermittently it reports the expected Changes Pending.

Error Messages:

[root@F5-2:Standby:Disconnected] config Dec 11 14:57:52 F5-2 emerg logger: Re-starting tmm Dec 11 14:57:52 F5-2 emerg logger: Re-starting tmm1 Dec 11 14:58:48 F5-2 emerg logger: Re-starting tmm Dec 11 14:58:49 F5-2 emerg logger: Re-starting tmm1 Dec 11 14:59:41 F5-2 emerg logger: Re-starting tmm Dec 11 14:59:41 F5-2 emerg logger: Re-starting tmm1 Dec 11 15:00:57 F5-2 emerg logger: Re-starting tmm Dec 11 15:00:57 F5-2 emerg logger: Re-starting tmm1 Dec 11 15:01:52 F5-2 emerg logger: Re-starting tmm Dec 11 15:01:52 F5-2 emerg logger: Re-starting tmm1 Dec 11 15:02:54 F5-2 emerg logger: Re-starting tmm Dec 11 15:02:54 F5-2 emerg logger: Re-starting tmm1

Just to follow up on this thread in-case anyone else finds it, the most recent comments where the issue relates to upgrading to 11.5.1 HF6 this is a known issue. F5 released an engineering fix for HF6 to resolve it and it's also now fixed in HF7. I've tested HF4 to HF7 and the issue is no longer present.

F5 has this documented as a software bug specific to HF6, but that's not necessarily true. We saw it on 11.5.1 HF4 that turned out to be related to a hardware failure. Now we're seeing it on 11.5.1 HF7, cause not yet determined. These are Viprion 2100 blades on a 2400 chassis.

For HF7 we see this in /var/log/ltm, which looks to me like a hardware problem. However, EUD passes all tests with flying colors.

May 21 14:24:11 slot1/sv2ltm02 info clusterd[24344]: 013a0007:6: clusterd starting up...
May 21 14:24:12 slot1/sv2ltm02 info clusterd[24344]: 013a0007:6: Chassis Id: chsXXXXXX, number of slots: 4, active slots: {1}, local slot: 1
May 21 14:24:12 slot1/sv2ltm02 info clusterd[24344]: 013a0023:6: Blade 1: No info received from slot: cannot connect to HAL
May 21 14:24:13 slot1/sv2ltm02 warning clusterd[24344]: 013a0005:4: Software Status table: local slot active entry missing
May 21 14:24:13 slot1/sv2ltm02 warning clusterd[24344]: 013a0005:4: Clusterd using /VERSION for SW specification