severity 600433 normal thanks On Sun, Oct 17, 2010 at 11:02:11AM -0200, Henrique de Moraes Holschuh wrote: > On Sun, 17 Oct 2010, Florian Forster wrote: > > On Sun, Oct 17, 2010 at 03:32:36AM -0200, Henrique de Moraes Holschuh wrote: > > > 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.
Is this still happening? I believe there were a few fixes that could be related to this in the past years. If it's still happening, we'll have to look into more details. Cheers, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
