<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2/15/2017 7:50 AM, Richard Hamilton
wrote:<br>
</div>
<blockquote
cite="mid:CAKsL-o6oTWKfcDCQ8-e5GPqnZEN6c2kw899qaXL95x6Mh=Ooow@mail.gmail.com"
type="cite">
<div dir="ltr">I noticed I was getting these when a host (marked
dialup) was down; turns out it's because there was an RPC test,
and rpcinfo has no option to choose a reasonable timeout; trying
to run it against a host that's down or unreachable takes nearly
ten minutes to time out!
<div><br>
</div>
<div>What I don't understand, is why, given the conn test was
enabled and not green or yellow, it was trying to do other
network tests on that host.</div>
<div><br>
</div>
<div>Here's the host line:</div>
<div>192.168.0.56<span class="gmail-Apple-tab-span" style="white-space:pre"> </span>lapple-sierra<span class="gmail-Apple-tab-span" style="white-space:pre"> </span>#
dialup CLIENT:lapple-sierra.pri noflap=location ssh ntp
rpc=mountd,nlockmgr,nfs,rpcbind,rquotad,status NOCOLUMNS:files
multihomed NOPROPPURPLE:+location NOPROPYELLOW:+cpu,+location<br>
</div>
<div><br>
</div>
<div>(location is an client extension script, not relevant to
the problem at hand)</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
<br>
Interestingly, this appears to be intentional -- dialup tests are
not considered "down" internally (clear is N/A more than a down
state) and so they aren't bypassed later in the cycle when we get to
running rpcinfo.<br>
<br>
I'm not entirely certain on the history here. This smells like it
should be a bug for precisely the reason you're seeing. Mass
timeouts testing against things that are down. OTOH, there may be
cases where things are intermittently unpingable and yet people are
expecting other testing to continue on. 'dialup' is a bit lesser
used nowadays, which may be why this is less frequently hit.<br>
<br>
There's logic in xymonnet that allows for internal flagging of
something as actually up or down for purposes of testing (to handle
things like badconn); this should probably become an option for
control in the future.<br>
<br>
Regards,<br>
-jc<br>
</body>
</html>