I recently ran into problems with generating TOTP 2-factor codes on my laptop. The fact that some of the codes would work and some wouldn't suggested a problem with time keeping on my laptop.
This was surprising since I've been running NTP for a many years and have therefore never had to think about time synchronization. After realizing that ntpd had stopped working on my machine for some reason, I found that systemd provides an easier way to keep time synchronized.
On a machine running systemd, there is no need to run the full-fledged ntpd daemon anymore. The built-in systemd-timesyncd can do the basic time synchronization job just fine. Attempting to restart the service did provide more details though:. The solution of course is to remove the former before enabling the latter:. Once the ntp package has been removed, it is time to enable NTP support in timesyncd.
For example, mine reads like this:. That may not be enough on your machine though. To check whether or not the time has been synchronized with NTP servers, run the following:. In Jessie, systemd-timesyncd put out some logging information to syslog, everytime that it pinged the time server that gave you a time stamp, time correction and frequency correction information.
With Stretch, these log reports have been suppressed. Does anyone know how to get them back? I can't find anything in the documentation. Thanks, Graham. You say you had to timedatectl set-ntp true after you got timesyncd running, but that's not working for me and I'm curious about how long I should spend watching it before I see a "Yes" in the NTP sync status, and I wonder what I might be missing if I'm not seeing this even though timesyncd appears to be running without errors.
I'm interested cause my NTP synchronized is always :no I done exactly the same commands on the blog and no change appears. The new systemd time synchronization daemon On a machine running systemd, there is no need to run the full-fledged ntpd daemon anymore. The solution of course is to remove the former before enabling the latter: apt purge ntp Enabling time synchronization with NTP Once the ntp package has been removed, it is time to enable NTP support in timesyncd.
Add a comment.Welcome to LinuxQuestions. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. But now, I have raspbian-stretch, and it doesn't use ntp but uses timesync, and systemctl grep sync gives me: Code:. Last edited by NotionCommotion; at AM.
Have you tried it to see what happens? Nothing says you can not go back to using ntp. Last edited by michaelk; at AM. Originally Posted by michaelk. The output of the status command should indicate the time server being used. I can not find any other default configuration file but then by systemd knowledge is limited It is shown there, but not where it is defined It has got to be somewhere!Logout Register. Solved Time sync problem. Solved Time sync problem Sat Sep 08, am Hi, I have had this problem with the pis not syncing time properly, all posts on forums are form years ago that I have found and really want to get this solved.
I want to make my wife a watering pi but need the clock to be correct for watering times. Even when I freshly configure the localisation settings, it still is 2 hrs slow. Could this be a bug for my time zone? Alternatively I suppose I could just train my wife to convert to utc.
Re: Time sync problem Sat Sep 08, pm If you're on Raspbian Stretch can you run Code: Select all timedatectl systemctl status systemd-timesyncd. Sep 09 squid systemd-timesyncd: Timed out waiting for reply from Re: Time sync problem Mon Sep 10, am looks like your not establishing a connection with the ntp servers set so perhaps check for local reliable ntp servers and set accordingly.
Re: Time sync problem Mon Sep 10, am Is there something in your network that blocks port ?
Raspberry Pi 4
Re: Time sync problem Tue Sep 11, am Is there a reason pi hole would block port ? I haven't touched the config of that, so it is all the default settings, I will disable it when I get home to test that one out. Run 'systemctl daemon-reload' to reload units. Sep 09 squid systemd-timesyncd: Timed out waiting for reply from 5. Had to output to file, as it goes nuts as naked command for some reason. This package uses the server's HTTP header contents to set system time, so it should be compliant with your current setup.
Not all websites send back enough information, if you get no date back try to specify another site. The date obtained is less accurate than from NTP servers, but it should be "good enough". Re: Time sync problem Tue Sep 11, am And it is fixed. Done Building dependency tree Reading state information Done The following NEW packages will be installed: htpdate 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get After this operation, Reading database Preparing to unpack Unpacking htpdate 1. Setting up htpdate 1. Processing triggers for man-db 2. Tried many many other methods, but all to no avail.Do you have issues with the time configuration on Raspberry Pi?
Or maybe you want to sync time with another server? How to sync time with a server on Raspberry Pi? Depending on your distribution and version, your Raspberry Pi may already have time sync enabled by default Use the command timedatectl to see the current configuration But most of the time you need to select the proper time zone and then the servers to use in the configuration And alternatively you can also use the Linux NTP services.
Before going further with technical information and commands, I want to introduce how the time synchronization works on Linux, on Raspberry Pi and on most of the modern devices. Before going further in the timedatectl configuration, I want to show you some useful commands you can use directly. And NTP is probably better on a server, to sync time with it and have more configuration options. NTP has less commands than timedatectl as everything is in the configuration file But you can use this one to manage the ntp server daemon:.
You now know how to change the date and time on your Raspberry Pi and how to synchronize the clock from several Linux computers on the same network.
Average rating 3. Vote count: 4. No votes so far! Be the first to rate this post. My goal is to help you with your Raspberry Pi problems using detailed guides and tutorials. Thanks for the information, but seems like timedatectl is not independent as I thought…it is still depend on ntp to carry out its operations.
Not a bug or a complaint, just a datapoint. It is not necessary to reboot the pi after changing the timesyncd. Just restart the service with the command:.
Your email address will not be published. Search Search for:. Table of Contents. Network Time Protocol source: Wikipedia. How useful was this post? Click on a star to rate it! We are sorry that this post was not useful for you! Let us improve this post!GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account. Since the above recent Arch ARM package updates, systemd-timesyncd never time syncs after boot. Rolling back the above versions fixes the problem. I rolled back and forward a few times to repeat this and confirmed it on my 2 RPi2 and 1 RPi3.
I updated my RPi1 also but the problem does not occur there may be timing related because RPi1 is much slower. Restarting systemd-timesyncd clears the problem.
The bug appears to have been introduced by commit 3e85ec0 which is from PR I compiled systemd for my RPi3 and proved that removing that change variable from the if statement in timesyncd-manager. I don't know the code well enough to propose the best way to guarantee the sync is forced but I can help with testing any proposed fix.
This problem occurred on the update I listed above to my 3 x RPi's all configured as generically as you could possibly get with systemd-networkd and simple DHCP clients. The RPi 3 uses a wifi connection, the 2 x RPi 2 use wired connections. No network. Have an old Beaglebone Black lying around which I installed Arch ARM with the offending systemd package and confirmed the same problem exists there.
I suspect this problem will occur on any system without a RTC. Thank you for the information.
How to sync time with a server on Raspberry Pi?
I do not know whether this is related to RTC or not. But now I am preparing a patch which fixes my previous commit. After submitting it as a PR, please test it.Plex Server on a Raspberry Pi 4!? (how to)
Thank you. I've created For the old way of doing things see this page. For the new way under Jessie read on. You can do this by uncommenting a line in config. Here are the magic incantation in a command window:. This will enable the i2c bus well it will on your next reboot. To tell the Raspberry Pi that we have a hardware clock, we need to add the following line to config.
This will stop that script exiting early and will update the clock on boot. If you set-up the RTC as decided above then by-and-large things should be tickety-boo. Disable this by doing:. Whilst working with the RTC, you may come up against a few things that will bite you. This can be pretty disconcerting, but is perfectly normal. It just means that the address 0x68 has been reserved for system use. The tips listed below can virtually all be done in other ways.
It drives me to distraction…. You can check that the pcf driver is loaded without a problem by looking to see whether it was loaded at the last boot:. Check the loading of the pcf driver. Checking and Setting the RTC. You can also enable the ntp service and get the current time with a sudo systemctl restart ntp. You can check the state of various services with the systemctl command. Here are some examples:. If you are troubleshooting strange clock syncs, the following command trawls the log for when the system updates the clock:.
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. After searching around, this method worked for me.
Subscribe to this blog
So by just typing this, the NTP support will be enabled:. If you set the Time Zone in raspi-config the Raspberry Pi will automatically update the time on boot, if connected to the internet. See forum post Time does not sync on Pi 3 and with official dongle. So that is quite similar to the other issue I and many others have with Raspberry Pi3 when operated over a Wi-Fi internal interface.
It should already be updating the time. Manual page for ntp. My son's Rasberry Pi would not update the time out of the box and after trying all the suggestions above I could get it to update manually but not automatically. Finally after looking elsewhere as well without success, I found that the ntp. That solved the problem for us.
It updates with both the WiFi and the ethernet cable. I don't know if it would update with WiFi without the change to rc. I found the timedatectl application to help me when I was having a similar issue. It's installed by default and '--help' gives a pretty good and simple overview of how to use the tool.
You don't need to use ntp to solve the issue. There is a script that reads the date from a server and you only need set the date to be the result of that script your Raspberry Pi needs to be connected to the internet.
Then, you need to run that command at startup.