During Resource negotiation, Foglight Agent Manager (FglAM) adds queue disk size settings from agent configuration to what is set in state/default/config/fglam.config.xml. If any of them is set to unlimited, the queue could grow to a size that will fit not into FglAM’s memory.
1) Stop FglAM service/daemon.
2) Delete the contents of <fglam home> /state/default/cache
3) Set max-disk-space to 50000 Kilobytes (50MB) in the VMware agent.manifest file.
a. Edit: <FGLAM_HOME>\agents\VMwarePerformance\<Version Number>\config\agent.manifest
b. Change max-dis-space values to “50000”/ , then save the file.
<upstream-queue type="upstream" max-queue-size="-1" max-disk-space="50000"/>
<upstream-queue type="upstream-verified" max-queue-size="-1" max-disk-space="50000"/>
4) Confirm FglAM max-disk-space values are default.
a. Navigate to <fglam_home>/state/default/config.
b. Open the file fglam.config.xml in a text editor.
c. Confirm max-disk-size is not unlimited (not -1) for any of the queues upstream, upstream-verified, or downstream.
Sample:
</config:documentation>
<config:upstream max-queue-size="-1" max-disk-space="2048" max-batch-size="2500" allow-runtime-change="true"/>
<config:upstream-verified max-queue-size="-1" max-disk-space="1024" max-batch-size="500" allow-runtime-change="true"/>
<config:downstream max-queue-size="-1" max-disk-space="2048" max-batch-size="2500" allow-runtime-change="true"/>
5) Delete the existing deployed negotiation configuration settings directory:
<FglAM_Home>/state/default/config/deployments
6) Restart the Agent Manager for these settings to take effect.Resolution:
STATUS:
Issue should be fixed under FAM-4116. Also new VMware agent 5.6.14 will have a limit of 50MB for its queue.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center