- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ntpd abort when time deviation goes over 1000s
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
тАО01-21-2011 09:41 AM
тАО01-21-2011 09:41 AM
We are facing the following issue...
Server XYZ(HPUX) time was modified manually, to be more than 1000s away from NTP server time.In this situation, when XYZ contacts NTP again, and detects such a high deviation, NTP daemon is aborted.
/var/adm/syslog/syslog.log shows
Jan 17 15:04:47 XYZ xntpd[24974]: time error -6405.921590 is way too large (set clock manually)
On according to SUN documentation:
"A sometimes confusing feature of NTP is that the NTP daemon on a client will abort itself if the offset between its clock and the serverтАЩs clock is too great. This behavior is triggered by an offset of greater than about 17 minutes. The rationale behind aborting the daemon over an excessive time error is that such a difference likely means that either the client is drifting at a very high rate, or the server has suddenly had its time changed using some method other than NTP."
Does this behavior happen also on HPUX?
Thanks in advance
-Andre
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2011 10:59 AM
тАО01-21-2011 10:59 AM
Re: ntpd abort when time deviation goes over 1000s
Yes it happened to me last week on an rx3600.
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2011 11:27 AM
тАО01-21-2011 11:27 AM
Re: ntpd abort when time deviation goes over 1000s
http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html
-g
Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log. This option can be used with the -q and -x options. See the tinker command for other options.
tinker panic 3600
in the configfile should put it to 1 hour.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2011 11:29 AM
тАО01-21-2011 11:29 AM
Solutiontinker panic 0
The 0 says ├в accept any offset├в which means that if your machine is suspended for a long time, as mine often are, when it unsuspends and gets a very large offset from the server everything will be OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2011 03:22 AM
тАО01-23-2011 03:22 AM
Re: ntpd abort when time deviation goes over 1000s
Yes what you are facing is typical NTP behaviour. If a drift of 1000 seconds is there between the server and client then, xntpd gives up and "kills" itself. That's how the protocol works. Janikks comments will be useful as well. Welcome to ITRC! Don't forget to assign appropriate points.
Regards
Ismail Azad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2011 02:55 AM
тАО01-24-2011 02:55 AM
Re: ntpd abort when time deviation goes over 1000s
Thanks a lot...
Br,
Andre