What happens when fglAM disconnects? (4309437)

When a Foglight Agent Manager (fglAM) host disconnects unexpectedly from the Foglight Management Server (FMS) due to a network outage - what is shown in the logs?

[1 ]Network connection (NIC) interrupted

[2] If the following shows Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): JVM_Bind this is caused by high network utilization.

In both cases the fglAM service or daemon will still show as active and running.

The following will show on the fglAM monitored host inside the log calledFglAM_YYYY-MM-DD_HHMMSS_00 under the directory $FGLAMHOME\state\default\logs

During network outage:

YYYY-MM-DD HH:MM:SS.SSS ERROR [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Client - Error transmitting message to upstream server http://yourfms:8080.
com.quest.glue.common.comms.CommunicationException: Could not send request to upstream host http://yourfms:8080

Caused by: java.net.NoRouteToHostException: No route to host: connect

YYYY-MM-DD HH:MM:SS.SSS ERROR [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Client - Error transmitting message to upstream server http://yourfms:8080.

After network interface has been restored:

YYYY-MM-DD HH:MM:SS.SSS INFO [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Connection - Network connection tohttp://yourfms:8080restored after 53 failed connection attempts.

YYYY-MM-DD HH:MM:SS.SSS VERBOSE [Upstream Polling-0] com.quest.glue.core.comms.transport.http.Client - Upstream message exchange took 109 ms which is far less than the maximum polling interval of 10,000 ms. Batch size has been increased to 20.