Forum Discussion

Rene_125890's avatar
Rene_125890
Icon for Nimbostratus rankNimbostratus
May 08, 2014

GTM emerg logger: Re-starting tmm1

We restarted a GTM.   After the reboot it started to send the message "emerg logger: Re-starting tmm1"   I haven't found a document that describes this issue related to a BIGIP GTM.  
availability
BIG-IP DNS
management
TMOS
John_Heyer_1508's avatar
John_Heyer_1508
Icon for Cirrostratus rankCirrostratus
May 21, 2015

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