Since I had to do this earlier today, I decided it would make a lot of sense to write it down for the next time that I need to do it. First, you’ll need to install NTP if it isn’t already installed.
For Debian or Ubuntu, that would be this command: You’ll find a lot of lines in there, but the important ones are the server lines.
# By default, exchange time with everybody, but don't allow configuration.
# ntpq -np remote refid st t when poll reach delay offset jitter ============================================================================== 220.127.116.11 1.14 2 u 30 64 7 108.518 -0.136 0.361 reply from .134: offset 6.715003 delay 0.041152, next query 30s reply from 2.34: offset 6.700224 delay 0.036263, next query 31s adjusting local clock by 6.734120s reply from .156: offset 6.708575 delay 0.035885, next query 30s reply from .134: offset 6.701463 delay 0.044199, next query 33s Got it. NTPd will "slew" your clock back into sync gradually.
We'll see differences between hardware clock and system clock # With the default settings below, ntpd will only synchronize your clock.
You can look there or refer to your hardware's documentation.
but the time never updates, it always stays on the incorrect time (it seems to be pulling time from the ESXi host on reboot unless i set it with ntpdate) I have unticked the box to get the time from the host. 1 u 22 64 377 8.661 -0.036 0.126 -ISP1 18.104.22.168 2 u 36 64 377 11.720 -0.027 0.280 #PRIVATE7 .
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.
Your server will # pick a different set every time it starts up.
Please consider joining the # pool: server 0.iburst server 1.iburst server 2.iburst server 3.iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/for # details. # # 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.