Ad Widget

Collapse

ICMP Ping: ICMP ping always returns 1 even on unreachable hosts

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • asentchernaev
    Junior Member
    • Nov 2020
    • 1

    #1

    ICMP Ping: ICMP ping always returns 1 even on unreachable hosts

    We noticed that after zabbix server and proxies have been upgraded from 4.4. to 5.0 a few days ago, ICMP checks are not working correctly any more - they show failed hosts still OK. Doesn't matter if host is reachable or unreachable - ICMP ping always returns 1. So trigger doesn't work too.

    All zabbix server and proxies are FreeBSD 12.1, zabbix components 5.0, fping 5.0

    We created especially for this troubleshooting new "fake" host with some not-existing IP address "172.16.100.67' which is part of one of our valid existing networks.And we point to one of zabbix proxies to monitor it.

    1. On proxy in debug mode (4) we see fping correctly finds 100% loss:

    45860:20201117:161427.145 End substitute_simple_macros_impl() data:'172.16.100.67'
    45860:20201117:161427.145 End of substitute_key_macros_impl():SUCCEED data:'icmpping[172.16.100.67,,,,]'
    45860:20201117:161427.145 In add_icmpping_item() addr:'172.16.100.67' count:3 interval:0 size:0 timeout:0
    45860:20201117:161427.155 In add_pinger_host() addr:'172.16.100.67'
    45860:20201117:161427.156 172.16.100.67
    45860:20201117:161428.163 read line [172.16.100.67 : [0], timed out (NaN avg, 100% loss)]
    45860:20201117:161429.163 read line [172.16.100.67 : [1], timed out (NaN avg, 100% loss)]
    45860:20201117:161430.160 read line [172.16.100.67 : [2], timed out (NaN avg, 100% loss)]
    45860:20201117:161430.160 read line [172.16.100.67 : - - -]
    45860:20201117:161430.162 host [172.16.100.67] cnt=3 rcv=3 min=0.000000 max=0.000000 sum=0.000000


    2. On zabbix server in default Debug mode there is nothing in zabbix server's log related to this host.

    3. In latest data of this object we see it stays "1" instead of "0" updating regularly. Correspondingly the trigger doesn't rise alarm.



    So we have lost one of the basic and the most widely used zabbix monitoring functionality.

    We tried the same from zabbix server itself - without proxy involved - the same result.

    We use the same "Template ICMP Ping" for a years. Then we updated it with the last official zabbix version - nothing changed.

    Also, creating manual icmpping check outside the template works in the same wrong manner.




    Last edited by asentchernaev; 19-11-2020, 23:16.
  • graham33
    Junior Member
    • Feb 2021
    • 2

    #2
    I'm having the exact same problem with Zabbix 5.0.3. Does anyone have any thoughts on how to resolve this?

    Comment

    • graham33
      Junior Member
      • Feb 2021
      • 2

      #3
      Here are the relevant logs:

      Code:
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 zbx_setproctitle() title:'icmp pinger #1 [pinging hosts]'
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 In do_ping() hosts_count:1
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 In process_ping() hosts_count:1
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 /tmp/zabbix_server_11742.pinger
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 192.168.1.179
      Feb 27 13:47:43 host zabbix_server[11742]: 11742:20210227:134743.933 /run/wrappers/bin/fping -C3 -i0 2>&1 </tmp/zabbix_server_11742.pinger
      Feb 27 13:47:44 host zabbix_server[11742]: 11742:20210227:134744.940 read line [192.168.1.179 : [0], timed out (NaN avg, 100% loss)]
      Feb 27 13:47:45 host zabbix_server[11742]: 11742:20210227:134745.941 read line [192.168.1.179 : [1], timed out (NaN avg, 100% loss)]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.051 read line [ICMP Host Unreachable from 192.168.1.74 for ICMP Echo sent to 192.168.1.179]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.051 read line [ICMP Host Unreachable from 192.168.1.74 for ICMP Echo sent to 192.168.1.179]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.051 read line [ICMP Host Unreachable from 192.168.1.74 for ICMP Echo sent to 192.168.1.179]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 read line [192.168.1.179 : [2], timed out (NaN avg, 100% loss)]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 read line []
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 read line [192.168.1.179 : - - -]
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of process_ping()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of do_ping():SUCCEED
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In process_values()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 host [192.168.1.179] cnt=3 rcv=3 min=0.000000 max=0.000000 sum=0.000000
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 In zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of zbx_preprocess_item_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.942 End of process_value()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.943 In zbx_ipc_socket_write()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.943 End of zbx_ipc_socket_write():SUCCEED
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.943 End of process_values()
      Feb 27 13:47:46 host zabbix_server[11742]: 11742:20210227:134746.943 End of process_pinger_hosts()

      Comment

      • dominicpratt
        Junior Member
        • Dec 2018
        • 14

        #4
        Same problem over here...

        Comment

        • Hamardaban
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • May 2019
          • 2713

          #5
          This is an issue of incompatibility between fping 5 and zabbix when running on freebsd. Fixed a long time ago. Update the zabbix version.

          Comment

          • dominicpratt
            Junior Member
            • Dec 2018
            • 14

            #6
            I'm running Zabnix 5.4.0 on Debian Buster.

            Comment


            • Hamardaban
              Hamardaban commented
              Editing a comment
              So you have a different problem that looks the same. Probably it was worth creating a separate forum thread because this one is about something else.
          • dimir
            Zabbix developer
            • Apr 2011
            • 1080

            #7
            This one was fixed in 5.0.5: https://support.zabbix.com/browse/ZBX-18365

            Comment

            Working...