Sponsored Content
Full Discussion: NTP problem
Operating Systems HP-UX NTP problem Post 41297 by Perderabo on Thursday 2nd of October 2003 07:53:29 AM
Old 10-02-2003
That behavior is normal. Or perhaps even abnormally good. xntp predicts the arrival of a packet from its peer. If that prediction is off by 128 milliseconds or more it gets mad and resyncs. When your peer is across the internet, that is guaranteed to happen several times a day. At least, that's what I thought....you must have an awesome isp or something.

I believe error messages until I have a sound reason to doubt them. If your peer is too far away, then your peer is too far away. The closer you are to your peer, the better. And best of all is to have your peer on the same lan.

Your dispersion is 10.01 which I think is great. I wouldn't worry until it gets close to 1000. At 1000 your system clock could be a full second off....I won't tolerate that. But people who sit around tuning ntp until the dispersion drops below one are crazy unless they work in astronomy or something.

Your setup could be improved quite a bit if you want to. You should have a ntp server outside of any firewalls and it should have 6 or 7 peers, not just one. Then your internal boxes should sync up with it.

And the Ultimate Solution.....
HP sold off all of its cool non-computer stuff Smilie I don't remember the name of the spin-off company. But they sell HP's old atomic clock. If you get that with the high performance cesium beam tube you will have a clock so accurate that no computer in existence can sync to it. It has a serial port and you can plug it in to your system and configure ntp to use it. That's the most accuracte clock available for sale as a product. Just a suggestion Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

NTP Authen Problem

Dear All I'm solaris user . I need to setup NTP authentication for my office server but I have some question for ntp setting up. I need to know if i set authen NTP the client that doesn't set for authen key can sync time from authen ntp server or not ?? when i setup the authen at ntp server ... (1 Reply)
Discussion started by: goasutlor
1 Replies

2. UNIX for Dummies Questions & Answers

NTP problem

All - i tried to sysn the clock from our server to get the timing and the server IP has been added in the ntp.conf file and i have some problems here. if some1 help me to solve this problem. 1. i can ping server 2. i was unable to ntpq -p (time out, no response from remote server, it looks... (2 Replies)
Discussion started by: March_2007
2 Replies

3. AIX

NTP Client problem

Hello everybody! When I run command "ntpdate" the following error occures "ksh: ntpdate: 0403-006 Execute permission denied. " # oslevel -s 5300-08-06-0918 oslevel -r 5300-08 eny suggestion friends? :-) (3 Replies)
Discussion started by: wwwzviadi
3 Replies

4. Red Hat

NTP sync problem

Hi, I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details. # service ntpd stop Stopping ntpd: ... (0 Replies)
Discussion started by: uday123
0 Replies

5. Solaris

NTP problem.

Hi, I have edited the /etc/inet/ntp.conf file to point to a new time server. When I restart ntp on Solaris 10 using 'svcadm disable/enable ntp' it still points to the old ntp server when I run a 'ntpq -p'. Any ideas? Thanks. Sparcman (4 Replies)
Discussion started by: sparcman
4 Replies

6. UNIX for Advanced & Expert Users

NTP Problem

Hello every one i want to setup a ntp on sco unix 5.0.6 and i don't have any time server how can i do this with local time (1 Reply)
Discussion started by: kaydream
1 Replies

7. Emergency UNIX and Linux Support

DNS and NTP strange problem

Hi, I'm having problem with my DNS and NTP. For the DNS: I'm using RHEL4, Bonding and heartbeat. Bond0 IP address: 192.168.1.10 Heartbeat or Bond0:0: 192.168.1.50 Currently, I use my heartbeat ip address for my DNS or in named.conf Everytime I reboot my server, it says that dns/named... (3 Replies)
Discussion started by: flekzout
3 Replies

8. AIX

NTP time problem

I got an ntp time problem on AIX server. os version is AIX7.1 OS LEVEL 7.1.0.0 i got below output,when i run the below command bash-3.2# ntpdate -dv XXXXXXXXXXXXXXXXXXXXXXXX 4 Dec 12:50:49 ntpdate: 3.4y transmit(xxxxxxxxx) receive(xxxxxxxxx) transmit(xxxxxxxx) receive(xxxxxxxxx)... (9 Replies)
Discussion started by: murali969
9 Replies

9. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies

10. UNIX for Beginners Questions & Answers

NTP synchronised problem in our Centos 7.6 node

Someone, please help on this issue:- Note : for security reason i didn't mention hostnames and ips. ============================================================================== # ntpstat unsynchronised polling server every 1024 s Ntpstat showing unsynchronised. ... (29 Replies)
Discussion started by: shanmugaraj
29 Replies
NTPDC(8)						      System Manager's Manual							  NTPDC(8)

NAME
ntpdc - monitor operation of ntp daemon SYNOPSIS
ntpdc [-n] [-v] hosts... DESCRIPTION
ntpdc sends an INFO_QUERY packet to an ntp daemon running on the given hosts. Each daemon responds with information about each of its peers, which ntpdc formats on the standard output. Normally, the name of the responding host and its peers are printed. The -n switch disables this, printing only internet addresses. Default is a terse, table-style report. The -t switch generates an alternate form of the terse report. The -v switch generates a verbose report. TERSE REPORT
A typical terse report looks like: (rem) Address (lcl) Strat Poll Reach Delay Offset Disp ========================================================================== -umd1 128.8.10.14 1 64 266 3.0 -65.0 0.0 *DCN1.ARPA 128.8.10.14 1 256 332 155.0 -4.0 0.0 128.8.251.92 128.8.10.14 2 64 367 -16.0 -61.0 0.0 idunno.Princeto 128.8.10.14 3 64 252 60.0 -53.0 0.0 leo 128.8.10.14 2 64 275 4.0 -273.0 1536.2 The alternate form is only slightly different; it looks like: Address Reference Strat Poll Reach Delay Offset Disp ========================================================================== -umd1 WWVB 1 64 266 3.0 -65.0 0.0 *DCN1.ARPA WWVB 1 256 332 155.0 -4.0 0.0 128.8.251.92 umd1 2 64 367 -16.0 -61.0 0.0 idunno.Prince trantor 3 64 252 60.0 -53.0 0.0 leo umd1 2 64 275 4.0 -273.0 1536.2 Fields are interpreted as follows: - or *: The - mark indicates a pre-configured peer (mentioned in ntp.conf). the * mark shows which pre-configured peer (if any) is cur- rently being used for synchronization. (rem) address: The remote host name or internet address of a peer. (lcl) address: The "local" host as specified as an argument to ntpdc. Reference: The reference time source being used for synchronization by the peer. Strat: The stratum level of the peer (as perceived by the local host). Poll: Current polling interval in seconds for this peer. Reach: Octal value of a shift register indicating which responses were received from the previous 8 polls to this peer (see RFC-????). Delay: Round-trip delay in milliseconds for this peer as of the latest poll. Disp: Current value of dispersion (see RFC-????) in milliseconds for this peer. VERBOSE REPORTS
When the -v flag is given a series of verbose reports are presented. A typical one looks like this: Neighbor address 128.4.0.6 port:123 local address 192.35.201.47 Reach: 0376 stratum: 1 poll int(HPI): 10 precision: -10 Sync distance: 0 disp: 0.014000 flags: 0 leap: 0 Reference clock ID: WWV timestamp: a7c2832e.6f9d0000 Poll int(MPI): 10 threshold: 1024 timer: 1024 send: 266 received: 192 samples: 9 Delay(ms) 1144.00 1296.00 1118.00 1115.00 1225.00 1129.00 1086.00 1087.00 Offset(ms) 19.00 92.00 -17.00 12.00 41.00 4.00 -1.00 -14.00 delay: 1086.000000 offset: -1.000000 dsp 0.014000 Fields are interpreted as follows: Neighbor address...: The address and port number of this neighbor, followed by the local address. Reach: nn Reachability in response to last 8 polls (octal value of shift register) stratum: n Stratum level. poll interval: time precision: nn The precision of this clock, given in seconds as a power of 2. e.g A clock derived from the power line frequency (60 Hz) has a pre- cision of 1/60 second (about 2^-6) and would be indicated by a precision of -6. Syn distance: 0 Synchronizing distance. Always zero in the current implementation. disp: nn Dispersion. flags: nn leap: flag The leap second indicator. Non-zero if there is to be a leap second added or subtracted at the new year. Reference clock ID: [address] timestamp: nn Poll interval: time threshold: nn timer: nn send: nn The number of ntp packets sent to this neighbor. received: nn The number of ntp packets received from this neighbor. samples: nn Delay and Offset The round-trip delay and clock offset for the last eight ntp packet exchanges. If there are fewer than eight valid samples, the delay field will be zero. delay: avg-delay offset: avg-offset dsp ??? Average delay, offset, and dispersion calculated from the above samples. Meanings...??? BUGS
Probably a few. Report bugs to Louis A. Mamakos (louie@trantor.umd.edu). SEE ALSO
RFC-???? Network Time Protocol(1), Dave Mills and ... ntpd(8), ntp(8) 10 March 1989 NTPDC(8)
All times are GMT -4. The time now is 03:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy