On 2016-03-17 10:23, Werner Flamme wrote:
Carlos E. R. [17.03.2016 10:13]:
You know the answer Carlos :-) because it hasn't managed to get a time signal from the ntp server.
That can't be.
monLanc:~ # rcntp status remote refid st t when poll reach delay offset jitter ============================================================================== Telcontar.valin .INIT. 16 u - 1024 0 0.000 0.000 0.000 -hora.ngn.rima-t 172.20.47.7 5 u 959 1024 377 14.444 0.862 2.787 *ntp.redimadrid. 193.147.107.33 2 u 43 1024 377 18.967 -0.387 0.586 +arthur.testserv 162.23.41.56 2 u 899 1024 377 57.548 0.607 0.346 -ntp.univ-angers 145.238.203.14 2 u 801 1024 337 60.726 -9.548 0.452 -x.ns.gin.ntt.ne 249.224.99.213 2 u 1051 1024 377 14.542 -9.265 1.013 +ms21.snowflakeh 162.23.41.55 2 u 732 1024 377 52.480 1.064 0.552 -62-210-28-176.r 84.255.209.79 4 u 990 1024 377 41.430 -4.797 0.778 -dnscache-london 145.238.203.14 2 u 1026 1024 377 57.125 -2.019 1.138
You did not show *this* output in your first mail. There were only two lines, stating that host AmonLanc.valino has not yet been reached. In this output, host Telcontar.valin has never been reached.
Both machines say the same: AmonLanc:~ # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== Telcontar.valin .INIT. 16 u - 1024 0 0.000 0.000 0.000 ... Telcontar:~ # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 74m 64 0 0.000 0.000 0.000 AmonLanc.valino .INIT. 16 u - 1024 0 0.000 0.000 0.000 ... the rest of the output I'm not insterested in, so I removed it. That's the meaning of the "...".
AmonLanc is the server, Telcontar is the client. The client says that the server is in INIT state and will not use it. And the server says the same of the client, see output above.
If Telcontar is a client, why does it show up in the given list? If AmonLanc is the server, why does it *not* show up in the given list? Judging from the output you show in this post, it is other way round.
Both machines are configured to use the other machine as client, but only AmonLanc is up full time, so I consider that one "server". The problem is here: # Access control configuration; see /usr/share/doc/packages/ntp/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. restrict 192.168.1.0 mask 255.255.255.0 notrust There is no access to machines in the LAN? This configuration is not mine, it was recommended after a vulnerability bug. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)