retitle 600433 collectd: rrd: issuing uc_update: Value too old messages thanks
On Sun, 17 Oct 2010, Florian Forster wrote: > On Sun, Oct 17, 2010 at 03:32:36AM -0200, Henrique de Moraes Holschuh wrote: > > collectd does not use UTC. > > collectd uses the timestamp returned by time(3). To the best of my > knowledge, it returns the number of seconds since 00:00:00 January 1st, > 1970 _UTC_ and should, as such, not be dependent on any timezone > setting. Indeed, time(2) does not suffer changes due to timezone and DST. > > collectd[2139]: uc_update: Value too old:name = > > <REMOVED>/temperature-temp1; value time = 1287260393; last cache update = > > 1287260393; > > If the timestamp was influenced by the timezone shift, "value time" > should be 1-3600 seconds smaller than "last cache update" [0]. The two > values are identical, though, which is 99.9% of all cases means that the > identifier ((file)name of the data) is not unique. Maybe the names If you mean the full path, then there is no colision. If you mean just the file-name (temperature-temp1), then there are many colisions. I don't think that was it. I did better checking now (heh, "repeats the error of the past" seems to apply to me very well...). It was a few hours away from the DST change, so my report was utterly bogus. I apologise for that. It happened three times, to all sensors, including those who would have no collision across different directories (i.e. unique filename). Looks more like collectd tried to store the same data twice. It all happened on the same "minute". Only other event of note is that cron started the cron.hourly scripts at that same minute, a few seconds earlier. However, I am _not_ seeing trouble every hour. Full ntp is running on this box, so time(2) is stable. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
