Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running ntpd server in my ubuntu (10.04) machine. But it is always stays in the 'INIT' state as shown below.

lyra@ws07475:~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
 europium.canoni .INIT.          16 u    - 1024    0    0.000    0.000   0.000

Of course, this means that it is not keeping time.

How can I start 'ntpd' server properly ? Please help.

share|improve this question

You only seem to have one server in your /etc/ntp.conf file. I have:


It would probably be a good idea to add at least a couple more.

However, I can reach (the first one), therefore I suspect that the problem is communication between remote sites and the ntp port (123). Firewalls can affect this, as can NAT translation.

Please check any firewall you might run, and consider setting up your nat (assuming you are running nat) to forward packets directed to port 123 to your server.

share|improve this answer

Sometimes internet routers have problems passing through NTP traffic. The reason is that UDP is a bit more tricker to forward and sometimes the port es even used on the device itself for a NTP daemon.

In my case it was a DD-WRT which blocked all of my NTP traffic. And as you might have noticed: NTP is not very good in saying that something went wrong. And especially not good in saying what went wrong. Here is the links to a thread about DD-WRT:

You can easily check if your Router is blocking NTP with the tool ntpdate (which is kind of a single use version of ntpd):

  • ntpdate - this call behaves like ntpd as long you run it as root and ntpd is not running at the same time. This command fails if your router blocks NTP
  • ntpdate -u - this call uses an unprivileged port, which much more likely works.

In case your router blocks NTP, what can you du?

Unfortunately, ntpd doesn't support any other way of communication than opening the port 123.

Fortunately, there are alternative implementations which use different ports:

I got good results with OpenNTPD, but in Forums people also recommended chrony

You can also setup just one OpenNTPD host and let all other machines in your network sync to this machine with their default NTP implementation.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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