Error initializing cmonit via `hyperledger/cello-analytics`

Just in case others run into this issue, this is currently what I experience after having configured an ELK node, Cello Master Node, and Cello Worker Node. All machines are running Ubuntu 16.04 LTS.

I first pulled down hyperledger/cello to the Cello Master and Worker node. I ran the perspective make commands on each and ensured they were working. I went as far as adding a host and activating a chain on the worker node within the Cello Dashboard. Cello is functioning fine.

I then pulled down hyperledger/cello-analytics to the ELK node and configured the indexing and dashboards by importing.

Next, I pulled down hyperledger/cello-analytics to the Cello Master and attempted to run bash start_cmonit.sh ES_NODE:9200 with the proper IP address of the ES node. The following is what I see:

18/04/26 21:39:08 21:39:08.302 1 ▶ INFO 001 Load config file: /go/src/github.com/yeasy/cmonit/cmonit.yaml
2018/04/26 21:39:08 21:39:08.303 1 ▶ INFO 002 Setting logging level=INFO
2018/04/26 21:39:08 21:39:08.303 serve ▶ INFO 003 Setting logging level=INFO
2018/04/26 21:39:08 21:39:08.319 monitTask ▶ INFO 004 >>>Start monitor task, interval = 5 seconds
2018/04/26 21:39:08 21:39:08.320 monitTask ▶ INFO 005 ===Synced task done: 1 hosts found
2018/04/26 21:39:08 21:39:08.320 Init ▶ ERRO 006 Cannot init connection to docker host=
2018/04/26 21:39:08 21:39:08.320 Init ▶ ERRO 007 unable to parse docker host ``
2018/04/26 21:39:08 21:39:08.320 monitTask ▶ WARN 008 <<Fail to init host cello-worker

I did some digging into the mongodb container to lookup data on the cello-worker host:

MongoDB Enterprise > db.host.find({})
{ "_id" : "3597a7cdef1f4b9cb7c4011bff1c891f", "name" : "cello-worker", "worker_api" : "tcp://10.99.222.175:2375", "create_ts" : ISODate("2018-04-25T19:29:07.661Z"), "status" : "active", "type" : "docker", "log_level" : "DEBUG", "log_type" : "local", "log_server" : "", "autofill" : false, "schedulable" : false, "capacity" : 1, "clusters" : [ "7f723acd510d40fe8a2834c4f449fa14" ], "vcparam" : {  }, "k8s_param" : {  } }

On the worker node, I can see docker is listening on the proper port via ps aux | grep docker:

root     15057  0.0  0.0  47004  3348 ?        S    Apr25   0:00 sudo dockerd -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --api-cors-header=* --default-ulimit=nofile=8192:16384 --default-ulimit=nproc=8192:16384 -D
root     15058  1.2  0.7 1130496 62440 ?       Sl   Apr25  13:37 dockerd -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock --api-cors-header=* --default-ulimit=nofile=8192:16384 --default-ulimit=nproc=8192:16384 -D

And to confirm that I can hit the worker node from the master node:

root@cello:/opt/cello-analytics/monitor# docker -H 10.99.222.175:2375 info
Containers: 17
 Running: 17
 Paused: 0
 Stopped: 0
Images: 11
Server Version: 17.05.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 100
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-112-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.784GiB
Name: cello-worker
ID: ADUH:2GQH:H4CF:MMRV:QMIO:6MR3:2UBA:CGAQ:PIN4:ZVVL:ZLPZ:PRBD
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 136
 Goroutines: 117
 System Time: 2018-04-26T15:37:03.721567364Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support