<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 9/1/2016 12:34 PM, Foster Patch
wrote:<br>
</div>
<blockquote
cite="mid:e0cf617d645849f7a2e6980ed1a06188@EXCH-02.accu.accuwx.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A change to how our DNS is configured has
caused the DNS test on xymonnet to reach around 50 seconds.
Combined with the other tests, the total time exceeds the time
limit (60). Because of this, xymonnet has been alarming for a
very long time. Is there any way I can adjust the time limit
to account for this? (Bring it up to 80 instead of 60 for
example) Here is our xymonnet section of tasks.cfg:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[xymonnet]<o:p></o:p></p>
<p class="MsoNormal"> ENVFILE
/usr/lib/xymon/server/etc/xymonserver.cfg<o:p></o:p></p>
<p class="MsoNormal"> NEEDS xymond<o:p></o:p></p>
<p class="MsoNormal"> CMD xymonnet --report --ping
--checkresponse --dns-timeout=5<o:p></o:p></p>
<p class="MsoNormal"> LOGFILE
$XYMONSERVERLOGS/xymonnet.log<o:p></o:p></p>
<p class="MsoNormal"> INTERVAL 1m<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any advice would be appreciated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:2.0pt;margin-right:0in;margin-bottom:2.0pt;margin-left:0in;text-autospace:none"><span
style="font-size:13.5pt;font-family:"Arial",sans-serif;color:#FF6600">Foster
Patch</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:2.0pt;margin-right:0in;margin-bottom:2.0pt;margin-left:0in;text-autospace:none"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Server
Technician</span><span style="color:#ED7D31">
</span></p>
</div>
</blockquote>
<br>
Hi Foster,<br>
<br>
The warning time passed in by xymonnet can be adjusted with the
--timelimit= option given in the CMD above. By default, it's
equivalent to the INTERVAL runtime (assuming xymonnet is run with
one, which it usually is), since it's there to let you know that the
testing interval isn't being met. You can also adjust that upwards
to match the average time things are taking.<br>
<br>
Unfortunately, DNS lookups-as-tests are handled differently from the
other tests, and timeouts or network problems can increase
xymonnet's runtime linearly with failures. Assuming the ones you're
testing are the only ones you need to test (i.e., remove dead
hosts), reducing '--dns-timeout' as low as you're comfortable with
is the only other real tweak here. Enabling/disabling the test
changes whether xymon considers an outage to be an alertable issue,
but doesn't prevent xymonnet from checking (and waiting on) that
service in the first place.<br>
<br>
If you have a large number of these with different SLAs, or a huge
number of DNS servers to test, there are advanced ways of setting up
xymonnet runtimes to isolate these effects. Basically, you'd set up
a separate instance of xymonnet just for doing DNS tests, while
excluding them from your normal install.<br>
<br>
<br>
HTH,<br>
-jc<br>
</body>
</html>