On Thu, Oct 27, 2011 at 10:18:13AM -0200, [email protected] wrote: > > > Hello! Anyone know if the heartbeat can change the time for a server? Because > when > it gets close to 30 days uptime simply migrate services to server1 server2. > Reviewing the logs you can > check that the time is > wrong. This timetable was > given before the problem occurred and > was correct. I think because of the time shift caused by the heartbeat > generated this error in the log.
You are using which version of heartbeat, on which platform? "bare metal" or "within some VM"? > Oct 27 10:22:09 inga heartbeat: [2313]: WARN: Gmain_timeout_dispatch: Dispatch > function for send local status was delayed 2998210 ms (> 10010 ms) before > being > called (GSource: 0x1f11370)Oct 27 10:22:09 inga heartbeat: [2313]: info: > Gmain_timeout_dispatch: started at 1965715369 should have started at > 1965415548Oct Please learn to paste ;-) > 27 10:22:09 inga heartbeat: [2313]: WARN: Late heartbeat: Node inga: interval > 3018270 ms Those "close to 30 days uptime" may not be rather close to 49 days? And you are using a 1000 Hz kernel? Or are you running within some VM, and those 30 days are your monthly backup run, which decided to freeze the VM for "as long as it takes", and it just took too long, like, 50 minutes? -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
