Machine Agent Bundle - 64-bit not reporting machine info statistics.

[CommunityUser]

Downloaded the Machine Agent Bundle - 64-bit windows (zip) (Standalone machine agent ZIP bundle with JRE to monitor your servers) for a Windows Server 2012 R2 in AWS EC2.

I configured the controller-info.xml file to use the correct controller host, controller port, account access key, account name along with the dotnet compatibility mode set to true.

I installed the JVM agent as a service. I see the two MachineAgentService.exe processes running.

I reviewed the log and seeing some entries:

[AD Thread-Metric Reporter0] 02 Aug 2017 17:44:27,881 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter0] 02 Aug 2017 19:28:27,882 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread Pool-Global0] 02 Aug 2017 19:33:28,497 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter1] 03 Aug 2017 00:44:27,872 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread Pool-Global0] 03 Aug 2017 01:53:42,435 ERROR SystemAgentPollingForUpdate - Fatal transport error while connecting to URL [/controller/instance/474251/systemagentpolling]: java.net.SocketException: Connection reset
[AD Thread Pool-Global0] 03 Aug 2017 01:53:42,435 WARN SystemAgentPollingForUpdate - Invalid response for configuration request from controller/could not connect. Msg: Fatal transport error while connecting to URL [/controller/instance/474251/systemagentpolling]
[Agent-Scheduler-1] 03 Aug 2017 01:54:26,718 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter1] 03 Aug 2017 02:14:27,912 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter1] 03 Aug 2017 06:04:29,283 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter0] 03 Aug 2017 11:46:18,188 ERROR ManagedMonitorDelegate - Fatal transport error while connecting to URL [/controller/instance/474251/metrics]: java.net.SocketException: Connection reset
[AD Thread-Metric Reporter0] 03 Aug 2017 11:46:18,188 WARN ManagedMonitorDelegate - Error sending metric data to controller:Fatal transport error while connecting to URL [/controller/instance/474251/metrics]
[AD Thread-Metric Reporter0] 03 Aug 2017 11:46:18,188 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Fatal transport error while connecting to URL [/controller/instance/474251/metrics]
at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:338)
at com.singularity.ee.agent.commonservices.metricgeneration.MetricReporter.run(MetricReporter.java:111)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
at java.lang.Thread.run(Thread.java:745)
[AD Thread Pool-Global0] 03 Aug 2017 11:46:27,120 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread Pool-Global0] 03 Aug 2017 11:54:28,925 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[Agent-Scheduler-1] 03 Aug 2017 14:54:58,958 INFO SystemAgent - Full certificate chain validation performed using default certificate file
[AD Thread Pool-Global0] 03 Aug 2017 14:59:59,872 INFO SystemAgent - Full certificate chain validation performed using default certificate file

Any ideas on why the java agent is not reporting the hard info statistics. Meaning CPU, Memory, Disk I/O, Network.

[CommunityUser · Accepted solution]

Reply, found out within the controller-info.xml file I had the change the <sim-enabled>false</sim-enabled> to <sim-enabled>true</sim-enabled>. Once this was done, I started to get Machine Stats populated within the Servers tab properly.