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
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
10 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT X11R4
timesyncd.conf
TIMESYNCD.CONF(5) timesyncd.conf TIMESYNCD.CONF(5)
NAME
timesyncd.conf, timesyncd.conf.d - Network Time Synchronization configuration files
SYNOPSIS
/etc/systemd/timesyncd.conf
/etc/systemd/timesyncd.conf.d/*.conf
/run/systemd/timesyncd.conf.d/*.conf
/usr/lib/systemd/timesyncd.conf.d/*.conf
DESCRIPTION
These configuration files control NTP network time synchronization.
CONFIGURATION DIRECTORIES AND PRECEDENCE
The default configuration is defined during compilation, so a configuration file is only needed when it is necessary to deviate from those
defaults. By default, the configuration file in /etc/systemd/ contains commented out entries showing the defaults as a guide to the
administrator. This file can be edited to create local overrides.
When packages need to customize the configuration, they can install configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/
are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. The main
configuration file is read before any of the configuration directories, and has the lowest precedence; entries in a file in any
configuration directory override entries in the single configuration file. Files in the *.conf.d/ configuration subdirectories are sorted
by their filename in lexicographic order, regardless of which of the subdirectories they reside in. When multiple files specify the same
option, for options which accept just a single value, the entry in the file with the lexicographically latest name takes precedence. For
options which accept a list of values, entries are collected as they occur in files sorted lexicographically. It is recommended to prefix
all filenames in those subdirectories with a two-digit number and a dash, to simplify the ordering of the files.
To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in the configuration
directory in /etc/, with the same filename as the vendor configuration file.
OPTIONS
The following settings are configured in the "[Time]" section:
NTP=
A space-separated list of NTP server host names or IP addresses. During runtime this list is combined with any per-interface NTP
servers acquired from systemd-networkd.service(8). systemd-timesyncd will contact all configured system or per-interface servers in
turn until one is found that responds. When the empty string is assigned, the list of NTP servers is reset, and all assignments prior
to this one will have no effect. This setting defaults to an empty list.
FallbackNTP=
A space-separated list of NTP server host names or IP addresses to be used as the fallback NTP servers. Any per-interface NTP servers
obtained from systemd-networkd.service(8) take precedence over this setting, as do any servers set via NTP= above. This setting is
hence only used if no other NTP server information is known. When the empty string is assigned, the list of NTP servers is reset, and
all assignments prior to this one will have no effect. If this option is not given, a compiled-in list of NTP servers is used instead.
RootDistanceMaxSec=
Maximum acceptable root distance. Takes a time value (in seconds). Defaults to 5 seconds.
PollIntervalMinSec=, PollIntervalMaxSec=
The minimum and maximum poll intervals for NTP messages. Each setting takes a time value (in seconds). PollIntervalMinSec= must not be
smaller than 16 seconds. PollIntervalMaxSec= must be larger than PollIntervalMinSec=. PollIntervalMinSec= defaults to 32 seconds, and
PollIntervalMaxSec= defaults to 2048 seconds.
SEE ALSO
systemd(1), systemd-timesyncd.service(8), systemd-networkd.service(8)
systemd 237 TIMESYNCD.CONF(5)