Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [SOLVED] fping: hostname nor servname provided, or not known

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 1 Posters 9.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      carl 0
      last edited by

      The box info
      uname -a:
      FreeBSD dc2.fw.backup.localdomain
      8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:50:43 EDT 2013
      root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386

      : cat /etc/resolv.conf
      domain localdomain
      nameserver 208.67.220.220
      nameserver 8.8.8.8
      nameserver 8.8.4.4

      : ping bbc.co.uk
      PING bbc.co.uk (212.58.251.195): 56 data bytes
      64 bytes from 212.58.251.195: icmp_seq=0 ttl=116 time=5.087 ms
      64 bytes from 212.58.251.195: icmp_seq=1 ttl=116 time=4.885 ms
      64 bytes from 212.58.251.195: icmp_seq=2 ttl=116 time=4.896 ms
      ^C
      –- bbc.co.uk ping statistics ---
      3 packets transmitted, 3 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 4.885/4.956/5.087/0.093 ms

      : ping google.com
      PING google.com (173.194.41.142): 56 data bytes
      64 bytes from 173.194.41.142: icmp_seq=0 ttl=54 time=4.471 ms
      64 bytes from 173.194.41.142: icmp_seq=1 ttl=54 time=4.411 ms
      64 bytes from 173.194.41.142: icmp_seq=2 ttl=54 time=4.576 ms
      ^C
      --- google.com ping statistics ---
      3 packets transmitted, 3 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 4.411/4.486/4.576/0.068 ms

      traceroute to above hostnames works fine also.

      The problem

      : fping bbc.co.uk
      fping: hostname nor servname provided, or not known

      : fping google.com
      google.com error while sending ping: No route to host
      google.com is unreachable

      This seems to be isolated to fping which is installed as part of zabbix-proxy (1.8.8,2 pkg v1.1):

      : fping -v
      fping: Version 2.4b2_to $Date: 2002/01/16 00:33:42 $
      fping: comments to david@remote.net

      I cam across things suggesting problems relating to ipv6 and fping, but we are not using ipv6 and confirmed disabled in /etc/defaults/rc.conf

      Any ideas why fping under 2.0.3 doesn't seem to work?

      Many thanks,
      carl^

      1 Reply Last reply Reply Quote 0
      • C
        carl 0
        last edited by

        Resolved. I managed to get Zabbix-2 Proxy working in the end which uses fping-3.4 rather than fping-2 and this works fine.

        Had a small issue with proxy.db where I was getting "no such table" in /var/log/zabbix2/zabbix_proxy.log which was resolved by stopping zabbix service, rm -rf /var/db/zabbix2/proxy.db, start zabbix service (restarting zabbix service did not seem to have same affect).

        w00t :)

        1 Reply Last reply Reply Quote 0
        • C
          carl 0
          last edited by

          Final followup… I found zabbix-proxy2(2.x) wasn't backward compatible with zabbix-server(1.8.x) so I ended up removing zabbix-proxy2 and re-installing zabbix-proxy1, this caused the fping issue again.

          So:

          pkg_info | grep fping
          pkg_delete -f fping-2.4b2_1
          fetch http://files.pfsense.org/packages/8/All/fping-3.4.tbz
          pkg_add fping-3.4.tbz

          For some reason, "/usr/local/etc/rc.d/zabbix_proxy.sh restart" did not work correctly, so use stop and start separately.

          Sorted.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.