Re: [opennms-discuss] Problems with time after a shutdown

[Tarus B. <ta...@so...>]

Gary Banke said:
> I shutdown my OpenNMS server the other day to move it into our data
> center. When I powered it back up it had lost time because the battery
> is dead.  It took me a few minutes to determine the clock was way off
> and in the meantime several polls occurred.  I reset the clock and
> rebooted the server, but now I'm getting failed polls to some systems
> with errors like:
>
> 2003-03-28 10:48:10,316 ERROR [PollerScheduler-30 Pool-fiber0]
> IcmpMonitor: RRD database 'update' failed for <IP address>, reason:
> illegal attempt to update using time 1048877290 when last update time is
> 1805973451 (minimum one second step)

> How might I fix this?

Ooh, that's a good one. Prolly be a good idea to set OpenNMS up not to
start on boot for just this reason.

So, I assume the clock was off into the future? Seems odd (mine usually go
to Jan 1, 1970 when this happens). If the number of timeticks should be
104... versus 180... you'll have to get rid of those entries. The easiest
way is to blow away the entire file, but that has the downside of losing
all of the data.

I am out of town this weekend (this is being written from a hotel room
using a 26kpbs connection to the internet) but I'll check the RRDTool FAQ
and mebbe send a note to the users mailing list to see if there is an easy
way to fix this.

-T

-- 
Tarus Balog
Consultant
Sortova Consulting Group, http://www.sortova.com
+1-919-696-7625
ta...@so...