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
NTP is and was setup correctly. Will the rrdtool (in remote command mode) use
the time of the *server* it runs on? Or of the client? If it's running on
the server, NTP cannot possibly be the problem, because only 1 of 7
databases will have the mysterious time jump. My only conclusion is that the
ti
@lists.oetiker.ch
> [rrd-users-bounces+s.shipway=auckland.ac...@lists.oetiker.ch] on behalf of
> Otheus [otheus+...@gmail.com]
> Sent: Saturday, 25 February 2012 12:22 a.m.
> To: rrd-users@lists.oetiker.ch
> Subject: Re: [rrd-users] recover from logged incorrect time
>
> I have a rel
s.oetiker.ch
Subject: Re: [rrd-users] recover from logged incorrect time
I have a related problem.
On our server we're running RRDtool 1.4.4
Remote monitoring servers connect to the RRDtool via TCP socket; rrdtool is
configured on the server to run under xinetd in 'remote command'
I have a related problem.
On our server we're running RRDtool 1.4.4
Remote monitoring servers connect to the RRDtool via TCP socket; rrdtool is
configured on the server to run under xinetd in 'remote command' mode.
Everything works fine most of the time.
Once every few days, one or more servers
07 4:40 AM
To: Rob Conway
Cc: rrd-users@lists.oetiker.ch
Subject: Re: [rrd-users] recover from logged incorrect time
Hi Rob,
you can 'dump' and edit the xml to 'reset' the time ... but note,
that an rrdtool update is a rather complex operation, so reverting
it is equaly comp
Rob Conway wrote:
>I ahve a small emmbedded processor running rrdtools. When the unit
>starts up the time is incorrect and I have on a number of occasions
>had the system log data with a time stamp that is 10hrs in front of
>real time. When the clock is corrected rrd will not accept the data
Hi Rob,
you can 'dump' and edit the xml to 'reset' the time ... but note,
that an rrdtool update is a rather complex operation, so reverting
it is equaly complex and always coupled with some loss of data ...
better is to first make sure your time is right ...
cheers
tobi
Today Rob Conway wrote
I ahve a small emmbedded processor running rrdtools. When the unit starts up
the time is incorrect and I have on a number of occasions had the system log
data with a time stamp that is 10hrs in front of real time. When the clock is
corrected rrd will not accept the data until the time stamp is
