Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

On my Ubuntu 13.04 (using AWS). When I start a new machine or when I reboot my machine ntp does not start and I see the following in the syslog:

Jan 10 02:56:49 ntpd: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING

I also notice that before this ntpdate was used to adjust time

Jan 10 02:45:20 ntpdate[960]: adjust time server offset -0.000259 sec

I am not sure if this is a race condition or me missing something here, I would appreciate if anyone can help me out here.

Thanks

share|improve this question
add comment

2 Answers 2

up vote 1 down vote accepted

This is because the ntpdate is running when you try to start the server. I haven't found reasons why to leave it installed so you could remove it if you are using ntp daemon:

sudo apt-get remove ntpdate
share|improve this answer
add comment

I've seen this on Debian Jessie. The cause appears to be a race between /etc/init.d/ntp and /etc/network/if-up.d/ntpdate, both of which appear to contain logic to lock each other out that doesn't actually work.

I like having the ntpdate command available even though I rarely use it, so rather than uninstall ntpdate altogether I've just inserted

exit 0

as the second line of /etc/network/if-up.d/ntpdate, which makes it do nothing. My ntp daemon now starts successfully at boot time.

share|improve this answer
add comment

Your Answer

 
discard

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.