Check agent full scan fails on service but not in test or telnet

Troubleshooting
1

I am using check_mk_raw 1.6.0p20 on Centos 8.3
I have it working on all my hosts but one.
The ping test shows this:
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.039 ms

The Agent test shows this:
<<<check_mk>>>
Version: 1.6.0p20
AgentOS: linux
Hostname: XXXXX
AgentDirectory: /etc/check_mk
DataDirectory: /var/lib/check_mk_agent
SpoolDirectory: /var/lib/check_mk_agent/spool
PluginsDirectory: /usr/lib/check_mk_agent/plugins
LocalDirectory: /usr/lib/check_mk_agent/local
OnlyFrom: 127.0.0.1 192.168.1.2 10.160.19.62

<<>>
tmpfs tmpfs 264046072 4 264046068 1% /dev/shm
tmpfs tmpfs 264046072 64396 263981676 1% /run
tmpfs tmpfs 264046072 0 264046072 0% /sys/fs/cgroup
/dev/sda4 ext4 1815479908 7559264 1715629572 1% /
/dev/sda5 ext4 388462 202420 161466 56% /boot
/dev/sda6 vfat 153428 3060 150368 2% /boot/efi
tmpfs tmpfs 52809212 12 52809200 1% /run/user/24316
tmpfs tmpfs 52809212 8 52809204 1% /run/user/11190
tmpfs tmpfs 52809212 0 52809212 0% /run/user/21610
tmpfs tmpfs 52809212 0 52809212 0% /run/user/0
tmpfs tmpfs 52809212 4 52809208 1% /run/user/39778
<<>>
[df_inodes_start]
tmpfs tmpfs 66011518 2 66011516 1% /dev/shm
tmpfs tmpfs 66011518 6293 66005225 1% /run
tmpfs tmpfs 66011518 17 66011501 1% /sys/fs/cgroup
/dev/sda4 ext4 115343360 171774 115171586 1%
…
telnet from the monitoring server to the node also works.

but when I try to do a full scan I get:
Starting job…

  • FETCHING DATA
    [agent] Execute data source
    [agent] ERROR: Communication failed: [Errno 111] Connection refused
    [piggyback] Execute data source
    No piggyback files for ‘XXXXXX’. Skip processing.
    No piggyback files for ‘192.168.1.3’. Skip processing.
    Completed.

Ideas? Thanks.

2

Wrong configuration of the hostagent?
A datasource like an ESX Connection active without a rule so it is used for every host?
Ralf

3

It turned out there was host agent rule set to scan on the wrong port 6557 instead of 6556 we found it by searching for the hostname in “Host & Service Parameters” . None of us remember setting that, but it must have been one of the admins.
Thanks.

4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.