- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NTP Blues
Operating System - HP-UX
1753902
Members
10505
Online
108810
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-26-2002 02:19 PM
тАО06-26-2002 02:19 PM
NTP Blues
I am trying to set ntp on one client.
I have set stratum 11 on one server.
On one of the client I am trying to set ntp. But everytime it gives error as
"time error xxxxx.xxx is way too large (set clock manually)
If I set clock manually to that of stratum server(Though there will always be differnce of some miliseconds) the NTP runs for a while and again dies after giving above mentioned error. I do not want to run ntpdate as it forwards the clock. Currently the offset is 1841.xxxx sec.
How do make this server run NTP without having serious repcurssions?
Thanks in advance
I have set stratum 11 on one server.
On one of the client I am trying to set ntp. But everytime it gives error as
"time error xxxxx.xxx is way too large (set clock manually)
If I set clock manually to that of stratum server(Though there will always be differnce of some miliseconds) the NTP runs for a while and again dies after giving above mentioned error. I do not want to run ntpdate as it forwards the clock. Currently the offset is 1841.xxxx sec.
How do make this server run NTP without having serious repcurssions?
Thanks in advance
There is no substitute to HARDWORK
- Tags:
- NTP
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2002 02:32 PM
тАО06-26-2002 02:32 PM
Re: NTP Blues
Can you post the contents of ntp.conf file? Also please post the output of "ntpq -p" command.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2002 05:43 PM
тАО06-26-2002 05:43 PM
Re: NTP Blues
Anil,
This could be attributed to a number of things, such as a dead clock battery on the machine in question, or some severe network latency. I would start by posting the results of 'ntpq -p', your ntp.conf file and any xntpd errors in your syslog.
Take a chance to review your configuration with this documentation on NTP from HP:
http://docs.hp.com/hpux/onlinedocs/B2355-90147/B2355-90147.html
Also be sure you have the latest patches installed for NTP:
PHNE_23717 (10.x)
PHNE_23697 (11.0)
How old is the machine that is having the problem with keeping acurate time?
Hope that helps.
-Mike
P.S. - Don't forget to assign points to your responses.
This could be attributed to a number of things, such as a dead clock battery on the machine in question, or some severe network latency. I would start by posting the results of 'ntpq -p', your ntp.conf file and any xntpd errors in your syslog.
Take a chance to review your configuration with this documentation on NTP from HP:
http://docs.hp.com/hpux/onlinedocs/B2355-90147/B2355-90147.html
Also be sure you have the latest patches installed for NTP:
PHNE_23717 (10.x)
PHNE_23697 (11.0)
How old is the machine that is having the problem with keeping acurate time?
Hope that helps.
-Mike
P.S. - Don't forget to assign points to your responses.
The network is the computer, yeah I stole it from Sun, so what?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2002 09:20 AM
тАО06-27-2002 09:20 AM
Re: NTP Blues
ntp.conf
server 172.17.113.3 # local clock
fudge 172.17.113.3 stratum 10
NTP log
26 Jun 00:35:57 xntpd[9406]: logging to file /tmp/ntp.log
26 Jun 00:35:57 xntpd[9406]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
26 Jun 00:35:57 xntpd[9406]: precision = 6 usec
26 Jun 00:40:47 xntpd[9406]: synchronized to 172.17.113.3, stratum=11
26 Jun 00:40:47 xntpd[9406]: time error -883610986.145565 is way too large (set clock manually)
ntpq -p dbnode
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 10 l - 64 377 0.00 0.000 10.01
ntpdate -d dbnode --
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
server 172.17.113.3, port 123
stratum 11, precision -17, leap 00, trust 000
refid [127.127.1.1], delay 0.02580, dispersion 0.00000
transmitted 4, in filter 4
reference time: c0c5d005.cf65e000 Thu, Jun 27 2002 23:25:17.810
originate timestamp: c0c5d03c.7f1f5000 Thu, Jun 27 2002 23:26:12.496
transmit timestamp: c0c5c90a.17546000 Thu, Jun 27 2002 22:55:30.091
filter delay: 0.02600 0.02580 0.02580 0.02580
0.00000 0.00000 0.00000 0.00000
filter offset: 1842.405 1842.405 1842.405 1842.405
0.000000 0.000000 0.000000 0.000000
delay 0.02580, dispersion 0.00000
offset 1842.405320
27 Jun 22:55:30 ntpdate[18101]: step time server 172.17.113.3 offset 1842.405320 sec
Regards,
server 172.17.113.3 # local clock
fudge 172.17.113.3 stratum 10
NTP log
26 Jun 00:35:57 xntpd[9406]: logging to file /tmp/ntp.log
26 Jun 00:35:57 xntpd[9406]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
26 Jun 00:35:57 xntpd[9406]: precision = 6 usec
26 Jun 00:40:47 xntpd[9406]: synchronized to 172.17.113.3, stratum=11
26 Jun 00:40:47 xntpd[9406]: time error -883610986.145565 is way too large (set clock manually)
ntpq -p dbnode
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 10 l - 64 377 0.00 0.000 10.01
ntpdate -d dbnode --
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
receive(172.17.113.3)
transmit(172.17.113.3)
server 172.17.113.3, port 123
stratum 11, precision -17, leap 00, trust 000
refid [127.127.1.1], delay 0.02580, dispersion 0.00000
transmitted 4, in filter 4
reference time: c0c5d005.cf65e000 Thu, Jun 27 2002 23:25:17.810
originate timestamp: c0c5d03c.7f1f5000 Thu, Jun 27 2002 23:26:12.496
transmit timestamp: c0c5c90a.17546000 Thu, Jun 27 2002 22:55:30.091
filter delay: 0.02600 0.02580 0.02580 0.02580
0.00000 0.00000 0.00000 0.00000
filter offset: 1842.405 1842.405 1842.405 1842.405
0.000000 0.000000 0.000000 0.000000
delay 0.02580, dispersion 0.00000
offset 1842.405320
27 Jun 22:55:30 ntpdate[18101]: step time server 172.17.113.3 offset 1842.405320 sec
Regards,
There is no substitute to HARDWORK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP