Splunk AppDynamics

Analytics agent not starting on Machine Agent

Sergio_Mandujan
New Member

When trying to start analytics agent as a machine agent extension for log analytics, the agent send an eception:

localhost==> [system-thread-0] 08 Sep 2021 13:07:23,907 INFO InProcessLauncherTask - Starting to execute actual task with parameters [{csvMethodArgs=/opt/appdynamics/machine-agent/monitors/analytics-agent/conf/analytics-agent.properties, methodName=main, className=com.appdynamics.analytics.agent.AnalyticsAgent}]
localhost==> [system-thread-0] 08 Sep 2021 13:07:25,444 FATAL InProcessLauncherTask - Error occurred while attempting to load the task [{csvMethodArgs=/opt/appdynamics/machine-agent/monitors/analytics-agent/conf/analytics-agent.properties, methodName=main, className=com.appdynamics.analytics.agent.AnalyticsAgent}]
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_292]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_292]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_292]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_292]
at com.singularity.ee.agent.systemagent.task.util.InProcessLauncherTask.launch(InProcessLauncherTask.java:186) ~[machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.task.util.InProcessLauncherTask.execute(InProcessLauncherTask.java:150) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.task.analytics.AnalyticsAgentLauncher.execute(AnalyticsAgentLauncher.java:68) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.MonitorTaskRunner.runTask(MonitorTaskRunner.java:149) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.ScheduledTaskRunner.run(ScheduledTaskRunner.java:41) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.ManagedMonitorDelegate.setupEnvTask(ManagedMonitorDelegate.java:272) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.managed.ManagedMonitorDelegate.initializeMonitor(ManagedMonitorDelegate.java:212) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.NodeMonitorManager.readConfig(NodeMonitorManager.java:178) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.NodeMonitorManager.startAllMonitors(NodeMonitorManager.java:265) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.NodeMonitorManager.<init>(NodeMonitorManager.java:79) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.components.monitormanager.AgentMonitorManager.<init>(AgentMonitorManager.java:63) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.Agent.setupMonitorManager(Agent.java:486) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.Agent.startServices(Agent.java:393) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.SystemAgent.startServices(SystemAgent.java:79) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.singularity.ee.agent.systemagent.Agent.start(Agent.java:378) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at com.appdynamics.agent.sim.legacy.DefaultLegacyAgentRegistrationStateManager$1.run(DefaultLegacyAgentRegistrationStateManager.java:80) [machineagent.jar:Machine Agent v21.7.0-3160 GA compatible with 4.4.1.0 Build Date 2021-07-23 23:04:28]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_292]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_292]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_292]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_292]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_292]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_292]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]
Caused by: com.appdynamics.common.framework.util.EmbeddedModeSecurityManager$SuppressedSystemExitException: System exit cannot be performed here as the application is running in embedded mode
at com.appdynamics.common.framework.util.EmbeddedModeSecurityManager.checkExit(EmbeddedModeSecurityManager.java:65) ~[analytics-shared-common-21.7.0-2292.jar:?]
at java.lang.Runtime.exit(Runtime.java:108) ~[?:1.8.0_292]
at java.lang.System.exit(System.java:973) ~[?:1.8.0_292]
at io.dropwizard.Application.onFatalError(Application.java:130) ~[dropwizard-core-2.0.17.jar:2.0.17]
at io.dropwizard.Application.onFatalError(Application.java:117) ~[dropwizard-core-2.0.17.jar:2.0.17]
at java.util.Optional.ifPresent(Optional.java:159) ~[?:1.8.0_292]
at io.dropwizard.Application.run(Application.java:94) ~[dropwizard-core-2.0.17.jar:2.0.17]
at com.appdynamics.common.framework.AbstractApp.callRunServer(AbstractApp.java:270) ~[analytics-shared-framework-21.7.0-2292.jar:?]
at com.appdynamics.common.framework.AbstractApp.runUsingFile(AbstractApp.java:264) ~[analytics-shared-framework-21.7.0-2292.jar:?]
at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(AbstractApp.java:251) ~[analytics-shared-framework-21.7.0-2292.jar:?]
at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(AbstractApp.java:171) ~[analytics-shared-framework-21.7.0-2292.jar:?]
at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(AbstractApp.java:150) ~[analytics-shared-framework-21.7.0-2292.jar:?]
at com.appdynamics.analytics.agent.AnalyticsAgent.main(AnalyticsAgent.java:101) ~[analytics-agent.jar:?]
... 27 more

Thanks in advance for your help....

Labels (1)
0 Karma

Hiroki_Ito
Contributor

Thank you for posting to the community.

Could you please delete the file below and restart the machine agent?
/opt/appdynamics/machine-agent/monitors/analytics-agent/analytics-agent.id
 
The stale pid file can cause the error.
If this doesn't fix the issue, could you please check errors in analytics-agent.log?

Best Regards,
Hiroki
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...