<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Scott;<br>
<br>
The first thing I would check would be to see if any new devices have
been added to your SmokePing config around the time you started having
problems. If so, check the SmokePing logs for warnings that look like
"Warning: Polling took longer than the interval step." or something
similar.<br>
<br>
What could be happening is that at some point, you had X devices
monitored, and they took, for example, 298 seconds to scan. If you
added another device, all of a sudden it might take 302 seconds to
scan. If you had your scan cycles set to 5 minutes (300 seconds), this
means that SmokePing can't complete a round of scanning before another
one starts. This could definitely cause the problems you've been
seeing.<br>
<br>
If this is the case, the solution is to either lenghten the scan cycle,
remove some hosts, increase concurrency (although I don't think that's
supported in 1.x?), or upgrade to the current SmokePing series and
implement multiple monitors and/or master/slave.<br>
<br>
Cheers,<br>
Peter<br>
<br>
<br>
Scott Moseman wrote:
<blockquote
cite="mid:342d47870711121150h4bbe61d0j479f77a0f35e796b@mail.gmail.com"
type="cite">
<pre wrap="">We're running Smokeping 1.34. Yes, I'm aware its old, but it's been
deployed forever and it's been working fine. Lately we've been having
some weird issues with missed polls. I have attached a sample showing
the last 3 hours and it includes 3 missed holes. This happens across
every device in the Smokeping config. We have a script that runs
every 5 minutes to update the config if there's new entries and part
of that process is to verify the process is running (and restart, or
start, if necessary). It logs what's going on. When the config
updates and Smokeping restarts, there's never a gap. According to my
scripts, and looking at the age of the Smokeping process that's
running, these gaps were NOT caused by Smokeping having failed
execution. Also, I setup a ping tool to monitor the switch, router
and an external address every SECOND for awhile. There was never a
lack of connectivity during these gaps in Smokeping. Is there any
means to troubleshoot? I will enable the syslog function to see if it
provides any details about what's going on.
Thanks,
Scott
</pre>
<br>
<hr size="4" width="90%"><br>
<center><img src="cid:part1.01040703.04010809@alter3d.ca"></center>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
smokeping-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:smokeping-users@lists.oetiker.ch">smokeping-users@lists.oetiker.ch</a>
<a class="moz-txt-link-freetext" href="https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users">https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users</a>
</pre>
</blockquote>
<br>
</body>
</html>