Windows_Sytem agent crashes after running for 5 minutes. Windows System agent starts and then sto (77119)

Windows_Sytem agent crashes after running for 5 minutes. Windows System agent starts and then stops after running for a short time.

FMS 5.5.8, Fglam 5.5.4.2, OS Cartridge 5.5.4

We did not see any type of errors or warns in either the Windows_System Agent log or the Fglam log in debug mode. The agent would just start, start collecting, then 5 minutes later would stop.

Resolution was that we noticed the Windows_System agent Properties ('Edit Properties' in Agent Status dashborad) - the NT_SampleFreq_List - all the collections had been changed from their defaults to collect at 60 seconds.

We set all the collections back to the out-of-the-box collection frequencies. The agent then started up and kept running. We suspect that the agent was "running into itself" - that is, a set of collections would start, and before they were finished, the same set of collections would try starting again in 60 seconds - this was causing the agent to crash.

Here are the default collection frequency settings for the Windows_System agent (version OS Cart 5.5.4 and previous):

System_Table - 300
Top_CPU_Table - 300
Top_IO_Table - 300
Top_MEM_Table - 300
Logical_Disk_Table - 300
Physical_Disk_Table - 300
FileSys_Table - 1800
FileSrvr_Table - 1800
Network_Interface_Table - 300
TCPConnections_Table - 300
EventLog - 300
Server_Table - 300
Processor_Table - 300
Services_Table - 300

Some of the messages we did see in the Windows_System agent log were:

INFO [Windows_System_on_hosgmsmb01.rendic.local Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: RedirectorObject is present for collection of FileServerTable.Network_Errors
VERBOSE [stderr Reader] com.quest.glue.core.jfogbank.process.AgentProcess - Agent output stream stderr closed. The agent has most likely exited abruptly.
VERBOSE [stdout Reader] com.quest.glue.core.jfogbank.process.AgentProcess - Agent output stream stdout closed. The agent has most likely exited abruptly.
WARN [JFogbankAgent-2] com.quest.glue.core.jfogbank.JFogbankAgentImpl - The agent exited unexpectedly with code 199 (hex: c7)
ERROR [JFogbankAgent-2] com.quest.glue.core.jfogbank.JFogbankAgentImpl - The agent has crashed 4 times and is considered to have failed. It will not be restarted.
INFO [JFogbankAgent-2] com.quest.glue.core.services.AgentStatusServiceImpl - Agent failure reported
VERBOSE [Windows_System_on_hosgmsmb01.rendic.local AgentStatusService] com.quest.glue.core.agent.AgentInstance - Destroying agent
INFO [Windows_System_on_hosgmsmb01.rendic.local AgentStatusService] com.quest.glue.core.agent.AgentInstance - Destroyed agent