Hi,
I’ve similar ‘Unknown’ issue.
I have checkmk distributed monitoring setup with 1 master and 9 remote nodes.
When I wanted to add one more remote node, the master couldn’t recognize the new node and didn’t trigger the active changes process.
I’ve followed this guideline
Distributed monitoring - Scaling and distributing Checkmk, but the result is same.
If I modify any other remote node, the master node triggers the active changes process. But still the new remote node’s status is ‘Unknown’
All remote nodes are using port 6557. Master node can acess to the new node over telnet.
I’ve opened tcpdump to monitor the packages. If I modify any other remote node and submit ‘active changes’ button, all nodes have communication with master with on port 6557, but the new node has no traffic on port 6557.
Also, the new node doesn’t have distributed_wato.mk configuration file. Probably master node couldn’t push the required configs to the new node.
Do you have any recommendation?
OMD[newnode]:~$ omd version
OMD - Open Monitoring Distribution Version 2.0.0p16.cre
OMD[newnode]:~$ omd start
Temporary filesystem already mounted
Starting mkeventd...OK
Starting rrdcached...OK
Starting npcd...OK
Starting nagios...OK
Starting apache...OK
Starting redis...OK
Starting stunnel...OK
Starting xinetd...OK
Initializing Crontab...OK
OMD[newnode]:~$ netstat -lnp | grep 655
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:6556 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:6557 0.0.0.0:* LISTEN 116596/xinetd
OMD[master]:~$ telnet <newnode-IP-address> 6557
Trying <newnode-IP-address>...
Connected to <newnode-IP-address>.
OMD[newnode]:~/etc/check_mk/conf.d$ ls -l
total 8
-rw-r--r-- 1 newnode newnode 72 Jun 30 15:08 mkeventd.mk
-rw-r--r-- 1 newnode newnode 76 Jun 30 15:08 pnp4nagios.mk
drwxrwxr-x 2 newnode newnode 114 Jun 30 15:08 wato/
Thank you.