All of agents deployed to a Foglight Agent Manager (FglAM) are listed as Broken and Not Collecting Data.
When trying to activate the agent, status message Error: Activate Agent operation failed: not activateable agents are [AGENT_NAMME(agent id: AGENT_ID)], failed agents are [], timeout agents are [] is shown.
The FglAM log shows that agents were restored after the FglAM was started, but that agents were deleted shortly after the FglAM connected to the Foglight Management Server (FMS).
VERBOSE [Startup Thread] com.quest.glue.core.agent.PersistAgentStatesTask - Agent Restore completed in 500 milliseconds.
...
INFO [Startup Thread] com.quest.glue.common.comms.transport.http.Connection - Connected to remote server at https://fms.yourdomain.com:8443.
...
VERBOSE [FglAM:IncomingMessage[5]-7] com.quest.glue.core.comms.handlers.DeleteAgentListener - Deleting agent instance HostAgents/WindowsAgent/Monitor@hostname1 [VERSION-BUILD] [id: a2bb98a7-d971-39e9-a00f-0d05e29d4b8d].
VERBOSE [FglAM:IncomingMessage[5]-8] com.quest.glue.core.comms.handlers.DeleteAgentListener - Deleting agent instance HostAgents/WindowsAgent/Monitor@hostname2 [VERSION-BUILD] [id: 82cb6e54-6cba-3961-9b13-00f83eea6887].
The FMS log reports that the agents were deleted because they were deleted from the FglAM host when the FglAM was not connected:
VERBOSE [FglAM:IncomingMessageResponse[4]-43] com.quest.glue.adapter.service.RemoteHosts - [Agent Sync] Deleting agent HostAgents/WindowsAgent/Monitor@hostname1 on host FGLAM_HOST [id: 1836af88-a917-4cb8-b6a8-ed322146a300]. It was previously deleted on the server when the host was not connected.
VERBOSE [FglAM:IncomingMessageResponse[4]-43] com.quest.glue.adapter.service.RemoteHosts - [Agent Sync] Deleting agent HostAgents/WindowsAgent/Monitor@hostname2 on host FGLAM_HOST [id: 1836af88-a917-4cb8-b6a8-ed322146a300]. It was previously deleted on the server when the host was not connected.
The FglAM ID defined in the config:id element of the fglam.config.xml configuration file changed after using the fglam --configure utility.
The FglAM ID is associated with an agent when the agent is deployed to the FglAM; since the FglAM ID changed, the agents are not activatable.
Set the value of the config:id element in the fglam.config.xml file back to the original value and restart the FglAM.
The fglam.config.xml file is located in the %FGLAM_HOME%\state\default\config directory.
Following is an example of the config:id line from the fglam.config.xml file:
<config:id>1836af88-a917-4cb8-b6a8-ed322146a300</config:id>If a backup of the fglam.config.xml file is not available, the original FglAM ID can be determined from the information for one of the agents in Diagnostic Snapshot in a FMS support bundle.
Following is an excerpt from the DiagnosticSnapshot_YYYY_MM_DD_hhmmss.txt file showing the ID of the FglAM associated with the Monitor@hostname1 agent in the agent home field:
-- agent info --
...
~~~~ ~~~~
agentId: 21
agentON: com.quest.nitro.agent:namespace=HostAgents,agentName=a2bb98a7-d971-39e9-a00f-0d05e29d4b8d,agentId=21
adapter: FglAM
type: WindowsAgent
namespace: HostAgents
agent name: a2bb98a7-d971-39e9-a00f-0d05e29d4b8d
munged: false
host: FGLAM_NAME
display name: Monitor@hostname1
agent obj: null
obsolete: false
hidden: false
activated: true
activatable: true
deletable: false
supports getLogs: false
agent home: FGLAM_NAME#1cc18489-7ecc-473c-8379-44bc4e9836b5
version: AGENT_VERSION
build: AGENT_BUILD
lifecycle not presentIn the above example, the FglAM ID obtained from the agent home field is 1cc18489-7ecc-473c-8379-44bc4e9836b5. Multiple agents from the affected FglAM can be verified to ensure the FglAM ID is correct.