Forum Discussion
CirrostratusGTM went into unknown state
We got two GTM boxes running A/A in each DC respectively, had an issue today when one GTM went out of the network. I could not ping the box though it was UP and when connected via console I was getting below messages in the logs continuously popping up.
Apr 20 04:32:28 gtm-xxxxxx emerg logger: Re-starting lind Apr 20 04:32:28 gtm-xxxxxx emerg logger: Re-starting mcpd Apr 20 04:32:28 gtm-xxxxxx emerg logger: Re-starting lind Apr 20 04:32:30 gtm-xxxxxx emerg logger: Re-starting lind Apr 20 04:32:30 gtm-xxxxxx emerg logger: Re-starting mcpd
Got across a devcentral article https://devcentral.f5.com/questions/lost-gui-access-to-big-ip-4000 which mentioned similar issue, hence rebooted the box post which it came up fine.
Anyone knows what is the possible cause as support say nothing wrong in the logs and qkview. Would appreciate if someone has encountered similar issue and knows about the possible cause.
Two weeks back had upgraded the GTM's to BIG-IP 12.1.2 Build 0.0.249 Final Code.
IainThomson85_1Cumulonimbus
The thing I can only say with certainty... it shouldn't be doing that...
F5 Support should be able to give an answer, if they can't they generally pass it to their engineering teams to investigate for new bugs etc.
andrzej_bajcar_Nimbostratus
Hello. Did you received any answer from F5 Support. What was the cause ?
Maneesh_72711F5 support requested to run the EUD test. But as I did not encounter similar issue later hence have not ran the command.