- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: kernel: set_rtc_mmss: can't update from 59 to ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-26-2007 11:25 PM
тАО08-26-2007 11:25 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 12:27 AM
тАО08-27-2007 12:27 AM
SolutionThis 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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 12:29 AM
тАО08-27-2007 12:29 AM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 12:33 AM
тАО08-27-2007 12:33 AM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
I might add that running up2date on the system or simply upgrading to a newer kernel might also help with the message.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 01:00 AM
тАО08-27-2007 01:00 AM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
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 :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 05:43 PM
тАО08-27-2007 05:43 PM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
We have another small cluster that's been up since Jan though.. Not under load, so not real..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 08:12 PM
тАО08-27-2007 08:12 PM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
--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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 09:10 PM
тАО08-27-2007 09:10 PM
Re: kernel: set_rtc_mmss: can't update from 59 to 0
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com