[cricket-users] "50 hour" recording bug

From: the+cricket@llama.com
Date: Tue Nov 09 1999 - 10:16:42 PST


From: the+cricket@llama.com

On Tue, 9 Nov 1999 the+best@llama.com wrote:

Another 0.70 anomality, may exist in earlier versions as well.

I've noticed a problem where RRDTool doesn't record the data that
Cricket collects for one sample period every 50 hour interval
(using the default five-minute average) into the particular RRA
database file the ds is using.

This is a problem, as it causes the Alarm() routine to send a trap.
This explains the false alarms I was seeing every 50 hours for each
datasource I was graphing. Otherwise, people not using monitor-thresholds
won't notice, because one dropped sample isn't noticeable and the
data appears to be collected fine in the logfile. You can see the
missed entry by doing a rrdtool dump of the .rra file in question.

I'm not sure that this is a Cricket problem per se, but I just wanted
to see if anybody had run across it and has a solution or workaround,
as well as to warn you that this problem exists.

Take care,

--Sam

--------------------------- ONElist Sponsor ----------------------------

       Thinking about putting your business on the Web?
MindSpring Biz has helped over 100,000 businesses get their .com.
             Join MindSpring Biz and save $50!
<a href=" http://clickme.onelist.com/ad/mindspring4 ">Click Here</a>

------------------------------------------------------------------------



This archive was generated by hypermail 2b29 : Mon Mar 06 2000 - 19:01:06 PST