[fli4l] Kein Ping von remoten Hosts mit rrdtool

[Peter Schauder]

On Sun, 18 Sep 2016 11:45:57 +0200, Peter Schiefer
<newsgroup at lan4me.de> wrote:

Hallo Peter,
>
>Du nutzt also VDSL mit einem Modem
Ja
> 
>> Was meinst du mit DHCP-Client?
>
>Den DHCP-Client nutzt man als WAN-Zugang wenn man hinter einer Kabelbox
>oder hinter einem anderen Router hängt.
>
Nö, VDSL der Telekom mit 300HS und Fli
>
>kannst du mal bitte alle Meldungen des collectd aus dem syslog hier pasten
>(am besten das was im syslog steht nach dem boot des fli4l sowie dem ersten
>online gehen).
>
Sep 15 17:21:54 PetersRouter daemon.info collectd[25903]:
Initialization complete, entering read-loop.
Sep 15 17:21:54 PetersRouter daemon.warn collectd[25903]: ping plugin:
ping_host_add (www.eisfair.de) failed: getaddrinfo: Name or service
not known
Sep 15 17:21:54 PetersRouter daemon.warn collectd[25903]: ping plugin:
ping_host_add (www.google.de) failed: getaddrinfo: Name or service not
known
Sep 15 17:21:54 PetersRouter daemon.warn collectd[25903]: ping plugin:
ping_host_add (www.fli4l.de) failed: getaddrinfo: Name or service not
known
Sep 15 17:21:54 PetersRouter daemon.warn collectd[25903]: ping plugin:
ping_host_add (www.heise.de) failed: getaddrinfo: Name or service not
known
... VPN zum 192.168.112.121 noch nicht aktiv
Sep 15 17:22:15 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:22:15 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:22:40 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:22:40 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:05 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:05 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:30 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:30 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:55 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:23:55 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:24:20 PetersRouter daemon.warn collectd[25903]: ping plugin:
host 192.168.112.121 has not answered 5 PING requests, triggering
resolve
Sep 15 17:24:20 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:24:29 PetersRouter daemon.err collectd[25903]: ping plugin:
ping_send failed: Operation not permitted
Sep 15 17:24:35 PetersRouter daemon.notice collectd[25903]: ping
plugin: ping_send succeeded.
Sep 15 17:24:50 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
Sep 15 17:25:20 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve
... Wiederholungen, weil backup.schauder.dom nicht an ist
Sep 15 17:29:50 PetersRouter daemon.warn collectd[25903]: ping plugin:
host backup.schauder.dom has not answered 5 PING requests, triggering
resolve

Macht den Eindruck, als ob er beim Start die betroffenen Adressen
nicht auflösen kann....Ping von der Commandline geht aber stressfrei

Gruß Peter