Linux ntp not updating any new dating site discover
I am running raspbian wheezy, upgraded to all the latest packages.
The only custom package installed on it is Oracle's Java 8, everything else and its configuration is stock.
This was absolutely the solution to my problem, but I found it to be temporary until I rebooted.
Eventually I caught an error in the shutdown that it couldn't update the hwclock because the hw clock had a future date (no idea how that happened). That forced the update to the fake hardware clock and then on boot the time was at least close to the current so ntp could do it's job normally..
ntpdate will run when an ethernet interface is brought up, and set the time from an ntp server (see /etc/default/ntpdate).
If ntpd is running, ntpdate will do nothing, however ntpdate will run prior to ntpd at bootup - so this should work out to set the time at bootup as long as there's an ethernet connection.
NTP needs more than one server to compare against, vote and pick the 'best' time source from. Switches at this office that were not upgraded (3750) are getting NTP normally. Jan 8 .826 CST: ref D496EA59.756DBDF0 (.458 CST Tue Jan 8 2013). I have removed the ntp lines from the switch configuration and re-added them, and that has not changed anything. address ref clock st when poll reach delay offset disp~1.1 0.0.0.0 16 - 64 0 0.0 0.00 16000.* master (synced), # master (unsynced), selected, - candidate, ~ configured Clock is unsynchronized, stratum 16, no reference clocknominal freq is 119.2092 Hz, actual freq is 119.2092 Hz, precision is 2**17reference time is 00000000.00000000 (.000 CST Thu Dec 31 1899)clock offset is 0.0000 msec, root delay is 0.00 msecroot dispersion is 0.00 msec, peer dispersion is 0.00 msec I enabled NTP debugging for events, packets, and clock synchro.. NTPD is running ntpq -pcrv -bash-3.2# ntpq -pcrv remote refid st t when poll reach delay offset jitter ============================================================================== dc3.domai 10.1.1.2 2 u 29 64 377 0.567 -4263.4 10.392 ass ID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart, version="ntpd [email protected] Mon Dec 9 UTC 2013 (1)", processor="i686", system="Linux/3.10.23-xxxx-std-ipv6-32", leap=11, stratum=16, precision=-20, rootdelay=0.000, rootdispersion=2356.905, peer=0, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 .000, poll=6, clock=d81ce655.d5ce975b Mon, Nov 24 2014 .835, state=1, offset=0.000, frequency=-0.140, jitter=0.001, noise=0.001, stability=0.000, tai=0 Something looks to be broken in your time setup. I would check the 2 other boxes DC1 & 3 to ensure they are getting the correct time. 1 u 40 64 377 9.468 0.209 0.129 -PRIVATE3 188.8.131.52 2 u 12 64 377 6.943 -0.270 0.142 -PRIVATE5 .
Jan 8 .822 CST: rtdel 0000 (0.000), rtdsp 10001 (1000.015), refid 00000000 (0.0.0.0). Jan 8 .819 CST: org 00000000.00000000 (.000 CST Thu Dec 31 1899). Jan 8 .819 CST: NTP: rcv packet from 1.1 to 10.19.0.111 on Vlan1:.