Ntp not updating date

Thus, I use the NTP service to update the time to the current time. However, after startup, it still takes a couple of minutes until the time is updated, during which period I cannot work effectively with tar and make. UPDATE 2: I tried following the few suggestions that came in response to the 1st update, but nothing seems to actually do the job as required. Here's what I tried:. Using the above, the machine still starts at However, when doing this from command line once logged in via ssh , the clock gets updated as soon as I invoke ntpdate.

Last thing I did was to remove that from rc. This does update the clock as expected, and I get the true current time once the command prompt is available. However , this means that if the machine is turned on and no user is logged in, then the time never gets updates. I can, of course, reinstall the ntp service so at least the clock is updated within a few minutes from startup, but then we're back at square 1. So, is there a reason why placing the ntpdate command in rc.

Instead of ntpdate which is deprecated , use ntpd :. The -gq tells the ntp daemon to correct the time regardless of the offset g and exit immediately q after setting the time. Probably the ntp service is running, that's why ntpdate can't open the socket port UDP and connect to ntp server. Use timedatectl systemd service unit to set the time.

As others have pointed out the best solution is to instruct ntpd to ignore the panic threshold, which is seconds by default. You can configure the panic threshold in one of two ways:.

So far this is essentially what others have recommended however there is one more step I think you should take. Install the fake-hwclock program:. With fake-hwclock installed your machine will not start up thinking it is all over again. This means you can have a somewhat correct clock in case there are network issues when you boot up. NTPDate is probably erroring out on boot because ntpd is running on that socket.

You could also uninstall ntpd all together apt-get remove ntp and add a cron script to use ntpdate every hour or so. Note that some current Ubuntu based systems don't even use the NTP service by default now. On my Linux Mint 19 Ubuntu Since Therefore critical systems like time are managed through systemd.

To find what service your system is using run something like. For TechJS on For myself on Ubuntu Interestingly, I logged into a Cheers to Prashant, who solved that issue. I am running a raspbian debian wheezy on my raspberry pi, which doesn't have the hwclock. I found it handy to write a little script and run it after my internet interface is up, so that I am sure that the moment the network becomes available, the clock gets updated.

The ntpd algorithms discard sample offsets exceeding ms, unless the interval during which no [absolute value of] sample offset is less than ms exceeds s. The first sample after that, no matter what the offset, steps the clock to the indicated time.

In practice this reduces the false alarm rate where the clock is stepped in error to a vanishingly low incidence. Normally, ntpd exits if the offset exceeds the sanity limit, which is s by default. This can be turned off with the -g option:.

If the sanity limit is set to zero, no sanity checking is performed and any offset is acceptable. This option overrides the limit and allows the time to be set to any value without restriction; however, this can happen only once. After that, ntpd will exit if the limit is exceeded. This option can be used with the -q option. The local client accepts this time if this peer becomes the master.

Root delay is the delay in milliseconds to the root of the NTP setup. In the example, all three servers can be the root because they are at stratum 1. Root dispersion is the maximum clock time difference that was ever observed between the local clock and the root clock.

Refer to the explanation of 'disp' under the show ntp association section for more details. This is an estimate of the maximum difference between the time on the stratum 0 source and the time measured by the client; it consists of components for round trip time, system precision, and clock drift since the last actual read of the stratum source.

An additional factor is that each increment in stratum involves a potentially unreliable time server, which introduces additional measurement errors. The selection algorithm used in NTP uses a variant of the Bellman-Ford distributed routing algorithm in order to compute the minimum-weight spanning trees rooted on the primary servers. The distance metric used by the algorithm consists of the stratum plus the synchronization distance, which itself consists of the dispersion plus one-half the absolute delay.

Thus, the synchronization path always takes the minimum number of servers to the root; ties are resolved on the basis of maximum error. This is the time stamp of the NTP packet originator; in other words, it is this peer's time stamp when it created the NTP packet but before it sent the packet to the local client.

This is the time stamp when the local client received the message. The difference between org time and rcv time is the offset for this peer. In the example, master This is the round trip delay in milliseconds of each sample. This is the clock offset in milliseconds of each sample. This is the approximate error of each sample. These eight samples correspond to the value of the reach field, which shows whether the local client received the last eight NTP packets.

Terms already defined in the show ntp association section or the show ntp association details section are not repeated. Precision is determined automatically and is measured as a power of two. Loss of synchronization between NTP peers or between a master and client can be due to a variety of causes. NTP avoids synchronization with a machine whose time might be ambiguous in these ways:.

Use the debug ip packet command in order to check if NTP packets are received and sent. With both debug ip packet and debug ntp packets commands enabled, you can see the packets that are being received and transmitted, and you can see that NTP is acting upon those packets. For every NTP packet received as shown by debug ip packet , there is a corresponding entry generated by debug ntp packets. This is an example where NTP does not work on received packets. For NTP packets that are sent out, a corresponding debug ntp packets output is present, because the NTP process has to generate the packet.

The issue is specific to received NTP packets that are not being processed. So, the local machine cannot trust the accuracy of the time present in the packet, because it does not know how long it took for the packet to get here.

NTP is meticulous about time and will not synchronize with another device it cannot trust or cannot adjust in a way so that it can be trusted.

If there is a saturated link and buffering occurs along the way, the packets get delayed as they come to the NTP client.

So, the timestamp contained in a subsequent NTP packet can occasionally vary a lot, and the local client cannot really adjust for that variance. SNTP may not be much of an alternative because it is not widely supported in software. Monitor the reach value from the show ntp associations detail command. If it is set up correctly it will do it automatically - although it may take a few minutes. Linux raspberrypi 4. Show 1 more comment. It returns error "sudo: ntpd: command not found" — Pygmalion.

It is installed, I am not that ignorant : — Pygmalion. 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.

But the solution was a hwclock update force. 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. Show 3 more comments. This question is apparently being "recycled" for some reason, and so it seems appropriate to recycle some old answers also : The year is now Seamus Seamus You must find the file that controls that list and add the correct entry. StevenHigh: It does work if ntp is installed using apt.

I've not tried building NTP myself, so I'll take your word for it. As a suggestion, perhaps it would be more useful if you added your own answer to address this situation?

In particular, how is it that systemd-timesyncd "loses" ntp just because it's installed in a different directory. And more importantly, how could this be corrected? Seamus, When I attempted to add my own explanation, I had my comment excised and got yelled a for going "off-topic". I would LOVE to post an answer here on how to do that. Show 6 more comments. I2 Change Timezone option doesn't exist any more — mrded. It does exist, at least in Raspbian Buster. Next, reboot and check. It should list at least one server.

I use time. Step1: Retrieve the date from a server. Amjad Abujamous Amjad Abujamous 2 2 bronze badges. You may not need to use ntp but you should.

It's better, faster, more accurate, and the industry standard. Don't make up your own weird things when good standards exist please. Yes, this works nice in my work environment, where most ports other then 80 are blocked. Note: make sure your timezone is set properly, which this tool can do as well. Aug 5 pi-hole ntpd[]: ntpd 4. Doesn't work on minimal raspbian: Failed to start ntp. And ntpd doesn't exist either.

The Pi definitely eventually gains time. This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one. Start a New Discussion. Upgraded to 6. Clicking on "Apply" does not update the system time. From the command line:. Did the latest firmware upgrade shaft the NTP updating? Go to Solution.

Not as elegant as doing it through the GUI, but works. View solution in original post. Have you tried rebooting your NAS?