The LogFilter agent was attempted to be deployed to multiple hosts (either on Agent Status or Agent Hosts).
The process seemed to have failed, as the red X appeared in the agent create status box after attempting for several
minutes to process the agent creation request.
The FMS was then restarted, and all the agents that were attempted to be added, appeared under Agent Status.
But, both the HostName and the Version columns had "Not Available" as the values for all these agents.
After some time, both the HostName and Version appeared, it is unclear if another FMS restart was done to get this information to appear.
The same behavior was noticed when only one agent was added, a failed to create X, but the agent would be there in agent status with no
HostName or Version. After the FglAM was recycled, the agent appeared with the correct information.
After some investigation, these were the two issues noted:
1. The FMS JVM appears to be overloaded
The box was properly specked as per the Foglight Requirement documents
2. There is a communication problem from the FglAM end to the FMS.
Either the FglAM is not sending agent confirmation, or the FMS is not receiving it.
We were unable to confirm what the issue may be
This is what we did to resolve (or so it appears) the problem:
1. FMS JVM overload
Modified the foglight.config file and added these two parameters
foglight.vm.option2 = "-XX:NewSize=1024m";
foglight.vm.option3 = "-XX:MaxNewSize=1024m";
NOTE: The Xms and Xmx were set on this system originally to 6144 (both values) and then to 8192 (both values).
It is unclear at this time if the values were set back to 6144
2. FglAM communication
We modified the FglAM adapter on the Agent Properties dashboard
we changed the FglAM adapter property MaxPollsPerMinute from 500 to 2000.
