In attempts to synchronize time, following the advice to run $ sudo ntpd -qg. This does not terminate on its own, and the time is not updated.

How to debug this problem?

pi@raspberrypi:~ $ sudo /etc/init.d/ntp start
[ ok ] Starting ntp (via systemctl): ntp.service.
pi@raspberrypi:~ $ ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================  .INIT.          16 u    -   64    0    0.000    0.000   0.000   .INIT.          16 u    -   64    0    0.000    0.000   0.000    .INIT.          16 u    -   64    0    0.000    0.000   0.000  .INIT.          16 u    -   64    0    0.000    0.000   0.000

Here's what ntpq sees. I don't like this .INIT..

Testing UDP connectivity to one of those listed:

pi@raspberrypi:~ $ nc -v -u -z -w 3 0.pool.ntp.org 123
Connection to 0.pool.ntp.org 123 port [udp/ntp] succeeded!
  • What changes have you made that necessitated starting ntpd manually? By default, the Pi will connect automatically and sync the time. Please also post your ntpd.conf file. How is the Pi connected to the internet? What model Pi are you using? Apr 14, 2017 at 19:31
  • I did not start it manually. I stopped it to sync the time manually with ntpd -qg. ntpd.conf is stock. Raspberry Pi 3.
    – Sassa NF
    Apr 14, 2017 at 20:06
  • Recent Raspbian may be using timesyncd instead of ntpd.
    – scruss
    Apr 15, 2018 at 16:23

2 Answers 2


Debian 8, like many recent releases of major Linux distributions, now uses systemd to manage the daemons and servers, so you want to use systemctl status ntp to see whether it's currently running and the last few log messages and start, stop and restart in place of status above to perform those actions.

Keep in mind that ntpd can take several minutes to start synchronizing time after a restart.


I had the same problem when connecting the Pi to my Uni wired network. To solve I had to ask the IT guys to provide me the ntp pool server they use, edit the ntp.config file and the problem was solved. If you are connecting to a non-domestic network, that might be the source of the problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.