All collections of Foglight database agents unexpectedly stopped
There were repeated "Could not acquire Agent Lock" error messages logged for one agent in the FglAM log.
VERBOSE [IncomingMessage-35850] com.quest.glue.core.comms.handlers.AbstractAgentLockMessageHandler - Could not acquire an Agent Lock from DBO-agent needed before we can process the com.quest.glue.messages.schema.v1_3.SetAgentState_v1_3 message [msgId: a19081ca-ee7a-4695-8c35-6acd05f812be]. Requeuing message with a 10,000ms delay.
The "Could not acquire Agent Lock" error message indicates that a shared object that the FglAM is using to synchronize the communication with the agent is locked, so the FglAM can’t send new messages to the agent.
WORKAROUND #1:
Restarting the Fglam that the DBO agent is bound to resolves this issue.
WORKAROUND #2:
If a restart of the FglAM does not resolve the issue, a restart of the FMS as well has been found to resolve the issue in some environments.
