Hi,
since Core 95, 'ntp' doesn't seem to answer on client requests anymore - perhaps because of updating to 4.2.8p4. Hm.
But even going back to a fresh built 'ntp 4.2.8' made no difference on my testmachine(s). I always get "Server dropped: strata too high".
Example (running 4.2.8p4 on 'ipfire.localdomain'): ***SNIP*** root@Devel: /home/matz/ipfire-2.x # ntpdate -d 192.168.100.254 15 Dec 01:24:30 ntpdate[26181]: ntpdate 4.2.6p5@1.2349-o Wed Nov 11 18:01:07 UTC 2015 (1) Looking for host 192.168.100.254 and service ntp host found : ipfire.localdomain transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) 192.168.100.254: Server dropped: strata too high server 192.168.100.254, port 123 stratum 16, precision -19, leap 11, trust 000 refid [192.168.100.254], delay 0.02577, dispersion 0.00003 transmitted 4, in filter 4 reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000 originate timestamp: da19dc43.01566238 Tue, Dec 15 2015 1:24:35.005 transmit timestamp: da19dc44.cc7207e2 Tue, Dec 15 2015 1:24:36.798 filter delay: 0.02577 0.02579 0.02582 0.02579 0.00000 0.00000 0.00000 0.00000 filter offset: -1.79379 -1.79375 -1.79373 -1.79370 0.000000 0.000000 0.000000 0.000000 delay 0.02577, dispersion 0.00003 offset -1.793799
15 Dec 01:24:36 ntpdate[26181]: no server suitable for synchronization found ***SNAP***
This errors occur while using 'ntp 4.2.8p4' *or* '4.2.8' on 'ipfire.localdomain', the version made no difference, 'stratum' is always '16'.
Despite these strata-errors, the "server" itself can update without any problems:
***SNIP*** root@ipfire: /etc # ntpdate -du de.pool.ntp.org 15 Dec 00:48:28 ntpdate[21875]: ntpdate 4.2.8p4@1.3265-o Mon Dec 14 20:18:01 UTC 2015 (1) Looking for host de.pool.ntp.org and service ntp 192.53.103.108 reversed to ptbtime1.ptb.de host found : ptbtime1.ptb.de transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) transmit(89.163.209.233) receive(144.76.172.53) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) server 192.53.103.108, port 123 stratum 1, precision -22, leap 00, trust 000 refid [PTB], delay 0.04007, dispersion 0.00099 transmitted 4, in filter 4 reference time: da19d3cb.d20fbf88 Tue, Dec 15 2015 0:48:27.820 originate timestamp: da19d3d2.a08ac5ee Tue, Dec 15 2015 0:48:34.627 transmit timestamp: da19d3d2.a39e8511 Tue, Dec 15 2015 0:48:34.639 filter delay: 0.04083 0.04066 0.04007 0.04060 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02236 -0.02170 -0.02048 -0.01957 0.000000 0.000000 0.000000 0.000000 delay 0.04007, dispersion 0.00099 offset -0.020482
server 144.76.172.53, port 123 stratum 3, precision -23, leap 00, trust 000 refid [144.76.172.53], delay 0.04214, dispersion 0.01234 transmitted 4, in filter 4 reference time: da19d2fb.f8d1bb50 Tue, Dec 15 2015 0:44:59.971 originate timestamp: da19d3d2.d42c2e6a Tue, Dec 15 2015 0:48:34.828 transmit timestamp: da19d3d2.d6d148c4 Tue, Dec 15 2015 0:48:34.839 filter delay: 0.04286 0.04214 0.04231 0.23389 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02139 -0.02095 -0.01985 -0.11450 0.000000 0.000000 0.000000 0.000000 delay 0.04214, dispersion 0.01234 offset -0.020956
server 89.163.209.233, port 123 stratum 3, precision -23, leap 00, trust 000 refid [89.163.209.233], delay 0.03394, dispersion 0.00092 transmitted 4, in filter 4 reference time: da19d15f.0d42b45c Tue, Dec 15 2015 0:38:07.051 originate timestamp: da19d3d3.05c168f7 Tue, Dec 15 2015 0:48:35.022 transmit timestamp: da19d3d3.0a02eb7e Tue, Dec 15 2015 0:48:35.039 filter delay: 0.03455 0.03433 0.03424 0.03394 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02323 -0.02242 -0.02128 -0.02082 0.000000 0.000000 0.000000 0.000000 delay 0.03394, dispersion 0.00092 offset -0.020821
server 85.25.105.106, port 123 stratum 1, precision -17, leap 00, trust 000 refid [PPS], delay 0.07425, dispersion 0.00128 transmitted 4, in filter 4 reference time: da19d3a8.adbc01a3 Tue, Dec 15 2015 0:47:52.678 originate timestamp: da19d3d3.3cf52b90 Tue, Dec 15 2015 0:48:35.238 transmit timestamp: da19d3d3.3d370319 Tue, Dec 15 2015 0:48:35.239 filter delay: 0.07629 0.07425 0.07672 0.07477 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02879 -0.02791 -0.02810 -0.02581 0.000000 0.000000 0.000000 0.000000 delay 0.07425, dispersion 0.00128 offset -0.027912
15 Dec 00:48:35 ntpdate[21875]: adjust time server 192.53.103.108 offset -0.020482 sec ***SNAP***
After searching the web, I started analyzing the ntpq-output (pe, as, rv). To get this output, I had to comment the following line in '/etc/ntp.conf':
... restrict default nomodify noquery ...
With this line active, I always got timeouts.
Testing config (original) was:
***SNIP*** disable monitor restrict default nomodify noquery server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift ***SNAP***
***SNIP*** root@ipfire: /etc # ntpq ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l - 64 0 0.000 0.000 0.000
ntpq> as
ind assid status conf reach auth condition last_event cnt =========================================================== 1 17736 8011 yes no none reject mobilize 1
ntpq> rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Mon Dec 14 20:18:00 UTC 2015 (1)", processor="i686", system="Linux/3.14.57-ipfire-pae", leap=11, stratum=16, precision=-19, rootdelay=0.000, rootdisp=2.895, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 7:28:16.000, clock=da19d25b.fd7b7d78 Tue, Dec 15 2015 0:42:19.990, peer=0, tc=3, mintc=3, offset=0.000000, frequency=0.000, sys_jitter=0.000000, clk_jitter=0.002, clk_wander=0.000 ***SNAP***
Somehow it seems to me, that my server can't reach the time servers from 'de.pool.ntp.org' as he should!?
I must confess, right now, I don't know where to search anymore. I found a missing 'Util.pm' in ntp-rootfile, which lead to 'ntptrace' not working correctly, but this wasn't the solution to the strata-errors.
So - anybody got a hint where to look next?
Best, Matthias
P.S.: On top of everything: right after pushing to the 'ntp'-branch, 'people/mfischer/ipfire-2.x.git' mysteriously disappeared from 'http://cgit.ipfire.org/people/mfischer/ipfire-2.x.git/refs/heads'. And on 'git.ipfire.org' I'm completely gone. Someone up there doesn't like me anymore...? ;-))
Hi,
the entire ntp server situation is a bit troublesome at the moment.
I had a look around and found that the ntp service is not able to sync with the local clock. There is a patch available that fixes that.
On top of that some change in the configuration file is required so that the ntp server actually uses the local clock.
I hope that they will sort out these problems upstream soon.
Thanks for looking into that. Please check if my fixes work by downloading the nightly builds, etc.
http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=93d6eed9a48a509e910fb... http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=429524c0406baeddf270d...
Best, -Michael
On Tue, 2015-12-15 at 02:12 +0100, Matthias Fischer wrote:
Hi,
since Core 95, 'ntp' doesn't seem to answer on client requests anymore - perhaps because of updating to 4.2.8p4. Hm.
But even going back to a fresh built 'ntp 4.2.8' made no difference on my testmachine(s). I always get "Server dropped: strata too high".
Example (running 4.2.8p4 on 'ipfire.localdomain'): ***SNIP*** root@Devel: /home/matz/ipfire-2.x # ntpdate -d 192.168.100.254 15 Dec 01:24:30 ntpdate[26181]: ntpdate 4.2.6p5@1.2349-o Wed Nov 11 18:01:07 UTC 2015 (1) Looking for host 192.168.100.254 and service ntp host found : ipfire.localdomain transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) transmit(192.168.100.254) receive(192.168.100.254) 192.168.100.254: Server dropped: strata too high server 192.168.100.254, port 123 stratum 16, precision -19, leap 11, trust 000 refid [192.168.100.254], delay 0.02577, dispersion 0.00003 transmitted 4, in filter 4 reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000 originate timestamp: da19dc43.01566238 Tue, Dec 15 2015 1:24:35.005 transmit timestamp: da19dc44.cc7207e2 Tue, Dec 15 2015 1:24:36.798 filter delay: 0.02577 0.02579 0.02582 0.02579 0.00000 0.00000 0.00000 0.00000 filter offset: -1.79379 -1.79375 -1.79373 -1.79370 0.000000 0.000000 0.000000 0.000000 delay 0.02577, dispersion 0.00003 offset -1.793799
15 Dec 01:24:36 ntpdate[26181]: no server suitable for synchronization found ***SNAP***
This errors occur while using 'ntp 4.2.8p4' *or* '4.2.8' on 'ipfire.localdomain', the version made no difference, 'stratum' is always '16'.
Despite these strata-errors, the "server" itself can update without any problems:
***SNIP*** root@ipfire: /etc # ntpdate -du de.pool.ntp.org 15 Dec 00:48:28 ntpdate[21875]: ntpdate 4.2.8p4@1.3265-o Mon Dec 14 20:18:01 UTC 2015 (1) Looking for host de.pool.ntp.org and service ntp 192.53.103.108 reversed to ptbtime1.ptb.de host found : ptbtime1.ptb.de transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) receive(144.76.172.53) transmit(89.163.209.233) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) transmit(192.53.103.108) receive(192.53.103.108) transmit(144.76.172.53) transmit(89.163.209.233) receive(144.76.172.53) receive(89.163.209.233) transmit(85.25.105.106) receive(85.25.105.106) server 192.53.103.108, port 123 stratum 1, precision -22, leap 00, trust 000 refid [PTB], delay 0.04007, dispersion 0.00099 transmitted 4, in filter 4 reference time: da19d3cb.d20fbf88 Tue, Dec 15 2015 0:48:27.820 originate timestamp: da19d3d2.a08ac5ee Tue, Dec 15 2015 0:48:34.627 transmit timestamp: da19d3d2.a39e8511 Tue, Dec 15 2015 0:48:34.639 filter delay: 0.04083 0.04066 0.04007 0.04060 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02236 -0.02170 -0.02048 -0.01957 0.000000 0.000000 0.000000 0.000000 delay 0.04007, dispersion 0.00099 offset -0.020482
server 144.76.172.53, port 123 stratum 3, precision -23, leap 00, trust 000 refid [144.76.172.53], delay 0.04214, dispersion 0.01234 transmitted 4, in filter 4 reference time: da19d2fb.f8d1bb50 Tue, Dec 15 2015 0:44:59.971 originate timestamp: da19d3d2.d42c2e6a Tue, Dec 15 2015 0:48:34.828 transmit timestamp: da19d3d2.d6d148c4 Tue, Dec 15 2015 0:48:34.839 filter delay: 0.04286 0.04214 0.04231 0.23389 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02139 -0.02095 -0.01985 -0.11450 0.000000 0.000000 0.000000 0.000000 delay 0.04214, dispersion 0.01234 offset -0.020956
server 89.163.209.233, port 123 stratum 3, precision -23, leap 00, trust 000 refid [89.163.209.233], delay 0.03394, dispersion 0.00092 transmitted 4, in filter 4 reference time: da19d15f.0d42b45c Tue, Dec 15 2015 0:38:07.051 originate timestamp: da19d3d3.05c168f7 Tue, Dec 15 2015 0:48:35.022 transmit timestamp: da19d3d3.0a02eb7e Tue, Dec 15 2015 0:48:35.039 filter delay: 0.03455 0.03433 0.03424 0.03394 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02323 -0.02242 -0.02128 -0.02082 0.000000 0.000000 0.000000 0.000000 delay 0.03394, dispersion 0.00092 offset -0.020821
server 85.25.105.106, port 123 stratum 1, precision -17, leap 00, trust 000 refid [PPS], delay 0.07425, dispersion 0.00128 transmitted 4, in filter 4 reference time: da19d3a8.adbc01a3 Tue, Dec 15 2015 0:47:52.678 originate timestamp: da19d3d3.3cf52b90 Tue, Dec 15 2015 0:48:35.238 transmit timestamp: da19d3d3.3d370319 Tue, Dec 15 2015 0:48:35.239 filter delay: 0.07629 0.07425 0.07672 0.07477 0.00000 0.00000 0.00000 0.00000 filter offset: -0.02879 -0.02791 -0.02810 -0.02581 0.000000 0.000000 0.000000 0.000000 delay 0.07425, dispersion 0.00128 offset -0.027912
15 Dec 00:48:35 ntpdate[21875]: adjust time server 192.53.103.108 offset -0.020482 sec ***SNAP***
After searching the web, I started analyzing the ntpq-output (pe, as, rv). To get this output, I had to comment the following line in '/etc/ntp.conf':
... restrict default nomodify noquery ...
With this line active, I always got timeouts.
Testing config (original) was:
***SNIP*** disable monitor restrict default nomodify noquery server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift ***SNAP***
***SNIP*** root@ipfire: /etc # ntpq ntpq> pe remote refid st t when poll reach delay offset jitter ===================================================================== ========= LOCAL(0) .LOCL. 10 l - 64 0 0.000 0.000 0.000
ntpq> as
ind assid status conf reach auth condition last_event cnt
1 17736 8011 yes no none reject mobilize 1
ntpq> rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Mon Dec 14 20:18:00 UTC 2015 (1)", processor="i686", system="Linux/3.14.57-ipfire-pae", leap=11, stratum=16, precision=-19, rootdelay=0.000, rootdisp=2.895, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 7:28:16.000, clock=da19d25b.fd7b7d78 Tue, Dec 15 2015 0:42:19.990, peer=0, tc=3, mintc=3, offset=0.000000, frequency=0.000, sys_jitter=0.000000, clk_jitter=0.002, clk_wander=0.000 ***SNAP***
Somehow it seems to me, that my server can't reach the time servers from 'de.pool.ntp.org' as he should!?
I must confess, right now, I don't know where to search anymore. I found a missing 'Util.pm' in ntp-rootfile, which lead to 'ntptrace' not working correctly, but this wasn't the solution to the strata-errors.
So - anybody got a hint where to look next?
Best, Matthias
P.S.: On top of everything: right after pushing to the 'ntp'-branch, 'people/mfischer/ipfire-2.x.git' mysteriously disappeared from ' http://cgit.ipfire.org/people/mfischer/ipfire-2.x.git/refs/heads'. And on 'git.ipfire.org' I'm completely gone. Someone up there doesn't like me anymore...? ;-))
-
Matthias Fischer -
Michael Tremer