On Sat, 8 Aug 2015 23:30:26 +0200 Aurelien Jarno <aurel...@aurel32.net> wrote: > Hi, > > On 2015-07-01 21:08, Vincent Lefevre wrote: > > Package: sensord > > Version: 1:3.3.5-2 > > Severity: grave > > Justification: causes non-serious data loss > > > > It seems that sensord uses an inconsistent set of data for its > > RRD update, yielding data loss. "rrd update" no longer updates > > the sensord.rrd database: > > > > -rw-r--r-- 1 root root 82480 2015-05-13 00:25:00 /var/log/sensord.rrd > > > > due to the following errors seen in my /var/log/syslog file: > > > > [...] > > From what I have been able to get the problem is that when using a > single rrd file for all data, the number of columns (ie sensors) is > defined when the file is created. Therefore the upgrade of your kernel > changed the number of sensors, and caused this issue. > > From what I have been able to read in the documentation, one solution > would be to use the MULTIPLE mode of RRD, which create one file per > column or sensor. But this format is incompatible with the current one, > which means people will have to recreate their database, and possibly > the scripts extracting the data for them. > > I don't really know what is the solution for this bug, one might be to > stop shipping sensord in Debian as it is kind of dead upstream and not > build by default. > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > aurel...@aurel32.net http://www.aurel32.net > >
Hi, Sounds like we should just sensord now while it still "sort of works" rather than dragging on with it until it breaks irrevocably. Thanks, ~Niels
