topic Re: kernel: set_rtc_mmss: can't update from 59 to 0 in Operating System - Linux

kernel: set_rtc_mmss: can't update from 59 to 0

Robert-Jan Goossens — Mon, 27 Aug 2007 06:25:07 GMT

Dear admins,

I've got three systems reporting above error messages on a irregular bases. All three are on the same patch level. All systems have xntp configured and get the time from lan time gps servers (2X)

# uname -a
Linux lx00x7 2.4.21-47.EL #1 Wed Jul 5 20:46:55 EDT 2006 i686 i686 i386 GNU/Linux

Aug 5 14:00:00 lx00x8 kernel: set_rtc_mmss: can't update from 59 to 0
Aug 3 06:00:00 lx00x2 kernel: set_rtc_mmss: can't update from 59 to 0
Aug 1 11:00:00 lx00x7 kernel: set_rtc_mmss: can't update from 59 to 0

Any idear what could be the cause of these errors?

Thanks in advanced
Robert-Jan

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Steven E. Protter — Mon, 27 Aug 2007 07:27:21 GMT

Shalom,

This is probably caused by a variance between the hardware clock and the click kept by the OS.

Bet these systems have been running for a very long time.

Use hwclock command to put the hardware clock at the same time as the OS or software clock from xntpd.

SEP

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Stuart Browne — Mon, 27 Aug 2007 07:29:34 GMT

Wow, horrible mix-up between the kernel and NTP.

The long story is.. kernel 'tweak' gone haywire with regards to.. err.. stuff I have no idea what it means to tell the truth.. ;)

http://www.mailinglistarchive.com/fedora-list@redhat.com/msg47237.html

This seems promising though.

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Steven E. Protter — Mon, 27 Aug 2007 07:33:54 GMT

Shalom,

I might add that running up2date on the system or simply upgrading to a newer kernel might also help with the message.

SEP

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Robert-Jan Goossens — Mon, 27 Aug 2007 08:00:05 GMT

Hi Steven/Stuart,

uptimes
lx00x8 up 52 days
lx00x2 up 63 days
lx00x7 up 62 days

# hwclock -r
is reporting an average diff of -0.658771 seconds

I will try to set the HWClock tonight, and have some extra logging enabled.

Thanks,
Robert-Jan

Ps.
We have a project running to update the systems to the latest Redhat version(60+ systems) but that will take a few months.

Stuart, thanks for the link :-)

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Stuart Browne — Tue, 28 Aug 2007 00:43:42 GMT

I'd love to recipricate with some lovely uptimes, but we just moved all our servers to a new structure, thus the phased migration over the previous week or so means they've all just rebooted.. Most were up a year.

We have another small cluster that's been up since Jan though.. Not under load, so not real..

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Robert-Jan Goossens — Tue, 28 Aug 2007 03:12:03 GMT

Used the systohc option to sync the system time to the hardware clock.

--systohc
Set the Hardware Clock to the current System Time.

I think the time difference is now close enough.

# hwclock -r;date
Tue Aug 28 10:01:17 2007 -0.093787 seconds
Tue Aug 28 10:01:17 CEST 2007

I will keep a close eye on these systems for a few weeks.

Thanks for your support guys!
Robert-Jan

Stuart same here, we installed Update 8 a few months ago, some of these Linux servers run months (a year) without a reboot. But I have to add these systems are application servers specially installed for one or two apps.

Re: kernel: set_rtc_mmss: can't update from 59 to 0

Steven E. Protter — Tue, 28 Aug 2007 04:10:17 GMT

If I was right, the messages should stop.

Update 9 is released and we've tested the non rhcs portion of it and find it to be reasonable, though not problem free.

Regards,

SEP