Date: Tue, 2 Apr 2002 08:45:31 -0500 From: Dylan Carlson <absinthe@pobox.com> To: freebsd-questions@freebsd.org Subject: NIS & ping/trace annoyances Message-ID: <20020402134826.2273A1FD97B@mail.3path.com>
next in thread | raw e-mail | index | archive | help
Hello,
We're having a T1 outage at the moment, but I noticed that when we have a
loss of internet connectivity that it affects ping with regard to non-local
addresses. Given the message, it looks like a bad side-effect of using NIS.
(substitute 11.22.33.44 with any pingable address outside your local subnet)
sysmon1% ping 11.22.33.44
PING 11.22.33.44 (11.22.33.44): 56 data bytes
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
yp_match: clnt_call: RPC: Timed out
.... ad infinitum
and ping sticks around in the process table and continues to error out until
you kill it, or until your route/connectivity comes back. Traceroute
exhibits the same behavior.
strace reveals:
execve("/sbin/ping", ["ping", "11.22.33.44"], [/* 35 vars */]PIOCWSTOP:
Resource temporarily unavailable
execve("/usr/sbin/traceroute", ["traceroute", "11.22.33.44"], [/* 35 vars
*/]traceroute to 11.22.33.44 (11.22.33.44)PIOCWSTOP: Operation not permitted
Pinging addresses on the local subnet, however, works fine. This is kind of
annoying... is this a configuration problem of my own or is this a bug?
Happily running FBSD 4.5.
Thanks,
--
Dylan Carlson [absinthe@pobox.com]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020402134826.2273A1FD97B>