Ad Widget

Collapse

ICMP Ping failed, is "not supported"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Tenou
    Junior Member
    • Feb 2020
    • 17

    #1

    ICMP Ping failed, is "not supported"

    Hey there,
    I've got Zabbix running on a Ubuntu 18.04 LTS VM.
    For all Items regarding ICMP-Ping I'm getting the following error:
    Code:
    fping failed: /usr/bin/fping -C3 -i10 2>&1 </tmp/zabbix_server_1629.pinger;/usr/bin/fping6 -C3 -i10 2>&1 </tmp/zabbix_server_1629.pinger;
    Does anyone have an idea what the problem could be? Afaic, the permissions are all right.
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Perhaps show us the permissions on fping and fping6?

    Also: https://www.zabbix.com/forum/zabbix-...mission-denied

    Comment

    • Tenou
      Junior Member
      • Feb 2020
      • 17

      #3
      Here you go in regards to the permissions:
      Code:
      -rwsr-sr-x 1 root root 48000 Jan  2  2018 fping
      lrwxrwxrwx 1 root root     5 Jan  2  2018 fping6 -> fping

      Comment

      • tim.mooney
        Senior Member
        • Dec 2012
        • 1427

        #4
        You shouldn't need setgid-root when you have setuid-root on fping, but that's not the source of the issue.

        I'm not sure what the problem is. The only issue I note is that both fping and fping6 are using the same input file. Does that input file contain DNS names, or does it contain IP addresses? The reason I ask is that for my fping installation, if the file just has e.g. IPv4 addresses in it, then 'fping' works but 'fping6' complains "Address family for hostname not supported".

        Those input files are only on disk for a very brief time. Can you catch one and see what's in it, and then try run the two individual commands using a copy of the file?

        Comment

        • Tenou
          Junior Member
          • Feb 2020
          • 17

          #5
          Some hosts are using DNS, some IP addresses. It doesn't work with both. What I just remembered is, that this only occured after disabling IPv6 on the host. I've done that since IPv6 is not yet implemented fully and some functions didn't work properly with it.

          Comment

          • Tenou
            Junior Member
            • Feb 2020
            • 17

            #6
            Okay, so I took the time to do it right, configure and enable IPv6 properly and now it works fine again. Thanks for the help anyways!

            Comment

            Working...