Paul <[email protected]> wrote: > On Mon, Nov 10, 2014 at 4:43 AM, Rob <[email protected]> wrote: >> I compiled ntp-dev 4.2.7p448 on the CubieBoard2 (ARM processor) and added >> a "pool pool.ntp.org" line to the config. It does not work. > > What does the log say? You're looking for: Soliciting pool server A.B.C.D
There is currently no logging. It is a default Debian install. I added a logfile directive and this shows up when I restart the server: 10 Nov 15:31:07 ntpd[5587]: Soliciting pool server 81.4.121.228 ping 81.4.121.228 PING 81.4.121.228 (81.4.121.228) 56(84) bytes of data. 64 bytes from 81.4.121.228: icmp_req=1 ttl=59 time=11.0 ms 64 bytes from 81.4.121.228: icmp_req=2 ttl=59 time=9.16 ms After some time another line is logged: 10 Nov 15:32:11 ntpd[5587]: Soliciting pool server 5.200.6.34 ping 5.200.6.34 PING 5.200.6.34 (5.200.6.34) 56(84) bytes of data. 64 bytes from 5.200.6.34: icmp_req=1 ttl=58 time=11.8 ms 64 bytes from 5.200.6.34: icmp_req=2 ttl=58 time=11.3 ms The servers are reachable. But: pool.ntp.org .POOL. 16 p - 64 0 0.000 0.000 0.002 As a test I enter the above two addresses as server in /etc/ntp.conf and restart the server: +81.4.121.228 193.79.237.14 2 u 16 64 1 9.329 0.935 0.002 5.200.6.34 193.79.237.14 2 u 15 64 1 11.687 -2.787 0.002 So they are fine. > What does the pool name resolve to on the host? > Are the N resolved addresses reachable? It works perfectly fine when I enter one or more "server pool.ntp.org" lines in the config. The problem only occurs when I use "pool" instead of "server". _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
