I archived the rrd files on the last time this time-jump error occurred on Feb 29. In this instance, the times were off by more than a mere hour!
# ls -l -rw-rw-r-- 1 nobody nobody 29540552 Feb 29 21:38 frontstatus-3.rrd -rw-rw-r-- 1 nobody nobody 4665288 Feb 29 21:43 perftimes-3.rrd # date +%s --date="Feb 29 21:38" 1330547880 # rrdtool last frontstatus-3.rrd ; done 30546223178 # rrdtool last perftimes-3.rrd ; done 30546223178 Both of these files are generated through remote rrdtool execution -- a perl script on the remote host connects to the rrdtool running on this server. None of the other 6 servers showed such a clock skew. -- View this message in context: http://rrd-mailinglists.937164.n2.nabble.com/recover-from-logged-incorrect-time-tp1073160p7398215.html Sent from the RRDtool Users Mailinglist mailing list archive at Nabble.com. _______________________________________________ rrd-users mailing list rrd-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
