After restarting the Foglight Agent Manager (FglAM), some agents fail to activate. Affected agent packages show deployment errors, indicated by:
[FGLAM_HOME]/agents/[AGENT_PACKAGE_NAME]
with a suffix like _ERROR_[TIMESTAMP]
agent.manifest
file renamed to agent.manifest_error
Example:
The HostAgents
directory contains HostAgents_ERROR_1684251567135
, and inside it, agent.manifest_error
. The same issue is observed with the DB_Oracle
agent package.
The issue is caused by insufficient physical memory to accommodate the JVM heap size increase during agent package deployment.
Error Log Snippet:
ERROR [Startup Thread] DeploymentManager - Failed to build an AgentPackage...
Cause: The addition of 16 MB to the negotiated JVM Max heap size would adjust to 28 GB, which exceeds the total available physical memory of 26 GB. Rejecting memory request.
Note: Correcting the heap size in baseline.jvmargs.config
alone is not sufficient if the error state has already occurred. Other undocumented causes may also lead to this issue.
[FGLAM_HOME]/bin/fglam -q
[FGLAM_HOME]/state/default/config/baseline.jvmargs.config
and ensure heap size values are within physical memory limits.[FGLAM_HOME]/state/default/config/deployments
[FGLAM_HOME]/agents/[AGENT_PACKAGE_NAME]
and:
[VERSION]_ERROR_[TIMESTAMP]
directory to remove the error suffix[VERSION]/config
, rename agent.manifest_error
to agent.manifest
[FGLAM_HOME]/bin/fglam -d
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center