docker_monitor showing localhost in docker profile

Article Id: 131898

Status: Published

Updated On: 08-05-2019 07:24

Products:

DX Infrastructure Management , NIMSOFT PROBES

Issue/Introduction:

docker_monitor 1.47 has localhost come up as the docker instance as opposed to the actual system name. It's not loading any details for the docker instance.

Cause:

Found this in the docker_monitor.log file:

May 06 18:10:41:875 [Data Collector - clboh-sensor-h1, docker_monitor] Unexpected fatal error occurred during data collection against DataCollector for clboh-sensor-h1
May 06 18:10:41:876 [Data Collector - clboh-sensor-h1, docker_monitor] java.lang.ExceptionInInitializerError
    at com.nimsoft.vm.collector.StandardDeliverer.newNimQos(StandardDeliverer.java:445)
    at com.nimsoft.vm.collector.StandardDeliverer.sendNimQoS(StandardDeliverer.java:260)
    at com.nimsoft.vm.collector.StandardDeliverer.deliver(StandardDeliverer.java:96)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.deliver(ProbeDataCollector.java:178)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.collectData(ProbeDataCollector.java:715)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:255)
    at com.nimsoft.probe.framework.genprobe.GenProbeDataCollector.execute(GenProbeDataCollector.java:36)
    at com.nimsoft.vm.collector.DataCollector.run(DataCollector.java:151)
    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)
Caused by: java.lang.RuntimeException: (2) communication error, UnknownHostException: clboh-sensor-h1: clboh-sensor-h1: Name or service not known

The "Name or service not known" indicates an issue resolving the host "clboh-sensor-h1".

Environment:

docker_monitor 1.47
Robot OS: Linux

Resolution:

Review the /etc/host file. Confirm that the entries for the host are all accurate and up-to-date.