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
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
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
01-01-2013 05:00 AM
01-01-2013 05:00 AM
Dear All ,
We have recived the NTP related alert on 31 Dec 12 night .
xntpd[2279]: Unsynchronized, possible remote server failure or defective hardware clock
when i chekced the syslog
Oct 20 11:55:56 sxpx123 xntpd[1959]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Oct 20 11:55:56 sxpx123 xntpd[1959]: precision = 7 usec
Oct 20 12:00:46 sxpx123 xntpd[1959]: synchronized to 172.19.19.30, stratum=7
Jan 1 00:00:01 sxpx123 xntpd[1959]: leap second occurred, stepped time back 1 second
Jan 1 02:29:27 sxpx123 xntpd[1959]: synchronisation lost
Jan 1 02:41:37 sxpx123 xntpd[1959]: synchronized to 172.19.1.30, stratum=7
Jan 1 02:41:38 sxpx123 xntpd[1959]: time reset (step) 1.030062 s
Jan 1 02:41:38 sxpx123 xntpd[1959]: synchronisation lost
Jan 1 02:46:58 sxpx123 xntpd[1959]: synchronized to 172.19.19.30, stratum=7
after that is ysnchronised. So acn one help me to undetstand it . The alert which we got (xntpd[2279]: Unsynchronized, possible remote server failure or defective hardware clock) because of only (an 1 00:00:01 sxpx123 xntpd[1959]: leap second occurred, stepped time back 1 second)
Thanks!!!
Solved! Go to Solution.
- Tags:
- NTP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-01-2013 06:13 PM
01-01-2013 06:13 PM
SolutionA leap second is occasionally inserted into the world-wide clocks to compensate for the slightly longer time of the earth's rotation. Here's a couple of references:
http://en.wikipedia.org/wiki/Leap_second
http://www.timeanddate.com/time/leapseconds.html
NTP assumes that a properly operating time source will not suddently jump without notice. It turns out that the NTP protocol does have a mechanism for handling a leap second:
http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.14.
However, it appears that HP-UX/xntpd does not do anything with the leap second. As such, you'll see the out-of-sync message which then be corrected like any out of sync condition.
Here are a couple of discussions about HP-UX NTP and leap seconds:
http://h30499.www3.hp.com/t5/System-Administration/HP-UX-and-Tru64-leap-second-handling/td-p/5609135
So your system is fine. The pertubation was corrected automatically.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2013 03:01 AM
01-03-2013 03:01 AM
Re: ntp sync
Thank you much for your support and explaination
Regards,
prashanth