One of the most common causes of any agent package deployment failure is that the Agent Manager does not have enough memory available as required by the Agent package that is being deployed. Check for an error message similar to below in the latest Agent Manager log file:
2019-03-26 13:09:08.987 VERBOSE [FglAM:IncomingMessage[5]-31914] com.quest.glue.core.agent.AgentPackage - AgentPackage RapidRecoveryAgent created at deployment location C:\Quest\Foglight Agent Manager\agents\RapidRecoveryAgent\1.5.0-1.5.0-20181011-0950
2019-03-26 13:09:09.003 INFO [FglAM:IncomingMessage[5]-31914] com.quest.glue.core.deployment.DeploymentManager - Scanning for installed and recognized agent types in C:\Quest\Foglight Agent Manager\agents\RapidRecoveryAgent\1.5.0-1.5.0-20181011-0950.
2019-03-26 13:09:09.034 ERROR [FglAM:IncomingMessage[5]-31914] com.quest.glue.core.deployment.DeploymentManager - Failed to build an AgentPackage from C:\Quest\Foglight Agent Manager\agents\RapidRecoveryAgent\1.5.0-1.5.0-20181011-0950\config\agent.manifest. Cause: The addition of 5 GB to the negotiated JVM Max heap size would adjust to 15 GB, which would exceed the total available physical memory of 14 GB. Rejecting memory request.
com.quest.glue.core.resources.InvalidResourceSettingException: The addition of 5 GB to the negotiated JVM Max heap size would adjust to 15 GB, which would exceed the total available physical memory of 14 GB. Rejecting memory request.
at com.quest.glue.core.resources.types.impl.JVMMemoryResourceImpl.validateSizeValues(JVMMemoryResourceImpl.java:249)
at com.quest.glue.core.resources.types.impl.JVMMemoryResourceImpl.validateDeployment(JVMMemoryResourceImpl.java:172)
at com.quest.glue.core.agent.ResourceDeploymentChangeListener.validateManifestRuntimeSettings(ResourceDeploymentChangeListener.java:74)
at com.quest.glue.core.deployment.DeploymentManager.processAgentsDir(DeploymentManager.java:692)
at com.quest.glue.core.deployment.DeploymentManager.deployArchive(DeploymentManager.java:405)
at com.quest.glue.core.comms.handlers.DeployAgentArchiveListener.newDownstreamMessage(DeployAgentArchiveListener.java:111)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.quest.common.util15.ConcurrentListenerManager$Handler.invoke(ConcurrentListenerManager.java:169)
at com.sun.proxy.$Proxy33.newDownstreamMessage(Unknown Source)
at com.quest.glue.common.comms.queues.AbstractIncomingQueue.newDownstreamMessage(AbstractIncomingQueue.java:412)
at com.quest.glue.common.comms.queues.AbstractIncomingQueue.newMessage(AbstractIncomingQueue.java:346)
at com.quest.glue.common.comms.queues.MultithreadedIncomingQueue$Executor.call(MultithreadedIncomingQueue.java:261)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
.
.
.
.
2019-03-26 13:09:09.065 ERROR [FglAM:IncomingMessage[5]-31914] com.quest.glue.core.comms.handlers.DeployAgentArchiveListener - Failed to deploy agent archive
In this case allocate more memory to Agent Manager host and try deploying the agent package again.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center