On 2016-03-17 09:57, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
How can it be that a server type machine, after 22 hours running continuously since boot, has ntp still in INIT state?
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 The asterisk means it is syncing to that machine.
Run a tcpdump on port 123 to see the time traffic flowing back and forth.
Yes, there is some. AmonLanc:~ # tcpdump port 123 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 10:09:46.474278 IP AmonLanc.valinor.ntp > arthur.testserver.li.ntp: NTPv4, Client, length 48 10:09:46.532068 IP arthur.testserver.li.ntp > AmonLanc.valinor.ntp: NTPv4, Server, length 48 10:10:09.618938 IP Telcontar.valinor.ntp > AmonLanc.valinor.ntp: NTPv4, Client, length 48 10:11:14.619002 IP Telcontar.valinor.ntp > AmonLanc.valinor.ntp: NTPv4, Client, length 48 10:11:38.474259 IP AmonLanc.valinor.ntp > ntp.univ-angers.fr.ntp: NTPv4, Client, length 48 10:11:38.536738 IP ntp.univ-angers.fr.ntp > AmonLanc.valinor.ntp: NTPv4, Server, length 48
Maybe also clarify for us which is the ntp server and which is the client that doesn't sync.
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. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)