-----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? I noticed it when running "rcntp status" on another machine in the same LAN: Telcontar:~ # rcntp status remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 1266 64 0 0.000 0.000 0.000 AmonLanc.valino .INIT. 16 u - 1024 0 0.000 0.000 0.000 ... That says that it consider my local server, AmonLanc.valinor, to be stratum 16, unreliable! AmonLanc:~ # systemctl status ntpd.service ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Drop-In: /run/systemd/generator/ntp.service.d └─50-insserv.conf-$time.conf Active: active (running) since Wed 2016-03-16 11:38:56 CET; 22h ago Process: 2193 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ntp.service └─2253 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf Mar 16 11:38:56 AmonLanc ntpd[2251]: ntpd 4.2.6p5@1.2349-o Mon Apr 20 13:44:53 UTC 2015 (1) Mar 16 11:38:56 AmonLanc ntp[2193]: Starting network time protocol daemon (NTPD)..done Mar 16 11:38:56 AmonLanc ntpd[2253]: proto: precision = 0.389 usec Mar 16 11:38:56 AmonLanc ntpd[2253]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Mar 16 11:38:56 AmonLanc systemd[1]: Started LSB: Network time protocol daemon (ntpd). Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen and drop on 1 v6wildcard :: UDP 123 Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen normally on 2 lo 127.0.0.1 UDP 123 Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen normally on 3 eth0 192.168.1.15 UDP 123 Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen normally on 4 eth0 fe80::203:dff:fe05:17fc UDP 123 Mar 16 11:38:56 AmonLanc ntpd[2253]: Listen normally on 5 lo ::1 UDP 123 Mar 16 11:38:56 AmonLanc ntpd[2253]: peers refreshed Mar 16 11:38:56 AmonLanc ntpd[2253]: Listening on routing socket on fd #22 for interface updates Mar 16 11:38:56 AmonLanc ntpd[2253]: logging to file /var/log/ntp AmonLanc:~ # The ntp log only contains this for the current session: 16 Mar 11:27:18 ntpd[2640]: ntpd exiting on signal 15 16 Mar 11:32:45 ntpd[2295]: 0.0.0.0 c016 06 restart 16 Mar 11:32:45 ntpd[2295]: 0.0.0.0 c012 02 freq_set kernel -39.538 PPM 16 Mar 11:32:51 ntpd[2295]: Listen normally on 6 eth0 fc00::203:dff:fe05:17fc UDP 123 16 Mar 11:32:51 ntpd[2295]: Listen normally on 7 eth0 fc00::5856:d05c:16a3:8e16 UDP 123 16 Mar 11:32:51 ntpd[2295]: peers refreshed 16 Mar 11:32:51 ntpd[2295]: new interface(s) found: waking up resolver 16 Mar 11:35:03 ntpd[2295]: ntpd exiting on signal 15 16 Mar 11:38:57 ntpd[2253]: 0.0.0.0 c016 06 restart 16 Mar 11:38:57 ntpd[2253]: 0.0.0.0 c012 02 freq_set kernel -39.538 PPM 16 Mar 11:39:06 ntpd[2253]: Listen normally on 6 eth0 fc00::21e9:7f82:3220:fcad UDP 123 16 Mar 11:39:06 ntpd[2253]: Listen normally on 7 eth0 fc00::203:dff:fe05:17fc UDP 123 16 Mar 11:39:06 ntpd[2253]: peers refreshed 16 Mar 11:39:06 ntpd[2253]: new interface(s) found: waking up resolver 16 Mar 11:42:15 ntpd[2253]: 0.0.0.0 c615 05 clock_sync I don't know this moment how to find out what is hapening. I'm using 13.1. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbqbwcACgkQtTMYHG2NR9WJgwCcD3Po6vZXndtM5P1k9qZmkZXX MLIAnAtthlkd07yKN1tjxBKb0uhQnScl =aNcV -----END PGP SIGNATURE-----