Ad Widget

Collapse

Truenas Scale - Zabbix App Problems Fping/ICMP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Llanelwy
    Junior Member
    • Oct 2026
    • 3

    #1

    Truenas Scale - Zabbix App Problems Fping/ICMP

    Hi,

    I have just installed the Docker App for Zabbix on my Trunas Scale Homeserver. But i am running into some problems. All ICMP monitoring seems to fail. SNMP works fine however.

    I have had a poke about and went into the Shell for the Zabbix app. From the command line Ping works fine. However fping always shows Host Unreachable. Even when trying localhost.

    $ bash
    zabbix@f501d68535a1:~$ ls
    dbscripts enc enc_internal export mibs modules snmptraps ssh_keys ssl
    zabbix@f501d68535a1:~$ ping localhost
    PING localhost (::1) 56 data bytes
    64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.035 ms
    64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.047 ms
    64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.049 ms
    ^C
    --- localhost ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2004ms
    rtt min/avg/max/mdev = 0.035/0.043/0.049/0.006 ms
    zabbix@f501d68535a1:~$ fping localhost
    localhost is unreachable
    zabbix@f501d68535a1:~$
    ​

    I am sure this is a simple config error on my part, but I can't seem to find it. I have looked at the fping location in the zabbix_server config files. The only mention I can find is in zabbix_server_location.config Which i appear unable to edit or modify as there appears to be no editor in the docker container at all (vi, vim nano all appear to not be installed)


    ### Option: FpingLocation
    # Location of fping.
    # Make sure that fping binary has root ownership and SUID flag set.
    #
    # Mandatory: no
    # Default:
    # FpingLocation=/usr/sbin/fping

    FpingLocation=${ZBX_FPINGLOCATION}

    ### Option: Fping6Location
    # Location of fping6.
    # Make sure that fping6 binary has root ownership and SUID flag set.
    # Make empty if your fping utility is capable to process IPv6 addresses.
    #
    # Mandatory: no
    # Default:
    # Fping6Location=/usr/sbin/fping6

    Fping6Location=​
    Hope this is a quick fix and something i am just missing in the zabbix config somewhere. Thanks
  • Llanelwy
    Junior Member
    • Oct 2026
    • 3

    #2
    I realised I did not include my version info
    TrueNAS SCALE Version
    25.10.7 - Goldeye


    App version
    Name:
    zabbix
    App Version:
    7.4.15-ubuntu
    Version:
    1.0.42
    Source:
    apps.truenas.com/catalog/zabbix_community, github.com/zabbix/zabbix-docker

    Edit more info:

    While troubleshooting, I have found that if I right-click on a host and use the ping script, that also works ok. However, none of the templates that use ICMP ping seems to work.
    Last edited by Llanelwy; 21-10-2026, 16:55.

    Comment

    • MisterGlass
      Junior Member
      • Oct 2026
      • 2

      #3
      I'm new to Zabbix and have the same problem. ICMP Ping template doesn't work.
      In a terminal on the Zabbix server I can ping the hosts. And on the Zabbix website running the scripts Ping and Traceroute on the host work just fine.
      Am i doing something wrong?

      Click image for larger version

Name:	image.png
Views:	18
Size:	57.1 KB
ID:	517849

      Running Zabbix 7.4.15 docker app on Truenas 25.10.7

      Comment

      • Llanelwy
        Junior Member
        • Oct 2026
        • 3

        #4
        Sounds like we are in the same boat.

        I think it that this has to be a bug in this version as i am getting the same thing. From the shell, can you reach anything using the command fping?
        From what i have read, the system uses that, not the normal Ping command.

        Comment

        • MisterGlass
          Junior Member
          • Oct 2026
          • 2

          #5
          You are right, fping doesn't work and returns a unreachable. When I do a traceroute it is reachable. This doesnt give me a lot of confidence in Zabbix, if a simple icmp test can get broken in an update.

          $ fping 1.1.1.1
          1.1.1.1 is unreachable
          $ traceroute 1.1.1.1
          7 141.101.65.185 (141.101.65.185) 6.734 ms 141.101.65.184 (141.101.65.184) 6.398 ms 185.147.12.101 (185.147.12.101) 11.992 ms
          8 141.101.65.227 (141.101.65.227) 7.306 ms 141.101.65.241 (141.101.65.241) 22.789 ms 141.101.65.185 (141.101.65.185) 5.280 ms
          9 one.one.one.one (1.1.1.1) 7.568 ms 6.585 ms 141.101.65.239 (141.101.65.239) 5.934 ms​

          Even a ping to localhost is unreachable
          $ fping 127.0.0.1
          127.0.0.1 is unreachable
          ​
          Ping works ok:
          $ ping 1.1.1.1
          PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
          64 bytes from 1.1.1.1: icmp_seq=1 ttl=54 time=7.35 ms
          64 bytes from 1.1.1.1: icmp_seq=2 ttl=54 time=7.19 ms​

          The execution rights are set for all users
          $ ls -la /usr/bin/fping
          -rwxr-xr-x+ 1 root root 48080 Nov 26 2025 /usr/bin/fping​

          Now what?!

          Comment

          Working...