While running the Machine Agent, you may see the following error in the Machine Agent logs:
ERROR RawCollectorUtil - Could not collect raw data
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
at [Source: ; line: 1, column: 1]
at com.fasterxml.jackson.databind.JsonMappingException. from(JsonMappingException. java:148)
at com.fasterxml.jackson.databind.ObjectMapper._ initForReading(ObjectMapper. java:3747)
at com.fasterxml.jackson.databind.ObjectMapper._ readMapAndClose(ObjectMapper. java:3687)
at com.fasterxml.jackson.databind.ObjectMapper. readValue(ObjectMapper.java: 2714)
at com.appdynamics.sim.agent.extensions.servers.model. RawCollectorUtil.runCollector( RawCollectorUtil.java:101)
at com.appdynamics.sim.agent.extensions.servers.model. RawCollectorUtil.runCollector( RawCollectorUtil.java:67)
at com.appdynamics.sim.agent.extensions.servers.model. newlinux.NewLinuxRawCollector. collectRawData( NewLinuxRawCollector.java:62)
at com.appdynamics.sim.agent.extensions.servers.model. newlinux.NewLinuxRawCollector. collectRawData( NewLinuxRawCollector.java:36)
at com.appdynamics.sim.agent.extensions.servers.model. Server.collectAndReport( Server.java:43)
at com.appdynamics.sim.agent.extensions.servers. ServersMonitor.run( ServersMonitor.java:90)
at java.util.concurrent.Executors$RunnableAdapter. call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset( FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ ScheduledFutureTask.access$ 301( ScheduledThreadPoolExecutor. java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ ScheduledFutureTask.run( ScheduledThreadPoolExecutor. java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
ERROR RawCollectorUtil - The standard out from the collector script was:
WARN RawCollectorUtil - The error log from the collector script was: ERROR: missing ip
When this occurs, the Machine Agent is not able to collect machine-level metrics.
This error occurs when the IP command is not in the PATH for the Machine Agent user. Without the correctly configured PATH, it is impossible for the Machine Agent to use SIM to collect the network metadata.
To verify the root cause, run the following commands in the shell prompt on the server that runs the Machine Agent.
shell> ip a
shell > which ip
shell> echo $PATH
The following results confirm the root cause:
bash: ip: command not found
which ip /usr/bin/which: no ip in
no ip present is path
2) Set IP as an environment variable for the user who is running the Machine Agent.
/sbin
folder. /sbin/ip -V
returns ip version and if it returns then ip is in /sbin
./sbin
to PATH environment variable
3) Start the Machine Agent.