[pkg-ntp-maintainers] Bug#788014: Bug#788014: does not start at bootup

[Kurt Roeckx]

On Sun, Jun 07, 2015 at 10:11:41PM +0200, Evgeni Golov wrote:
> Package: ntp
> Version: 1:4.2.6.p5+dfsg-7
> Severity: important
> 
> Hi,
> 
> after upgrading this machine to jessie, ntpd does not start at boot.
> This might be systemd related.
> 
> root at genshi:~# systemctl status ntp
> ? ntp.service - LSB: Start NTP daemon
>    Loaded: loaded (/etc/init.d/ntp)
>    Active: active (exited) since Sun 2015-06-07 21:18:52 CEST; 31min ago
>   Process: 616 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
> 
> Jun 07 21:18:52 genshi.die-welt.net ntpd[648]: ntpd 4.2.6p5 at 1.2349-o Fri Apr 10 19:04:04 UTC 2015 (1)
> Jun 07 21:18:52 genshi.die-welt.net ntpd[650]: proto: precision = 0.161 usec
> Jun 07 21:18:52 genshi.die-welt.net ntp[616]: Starting NTP server: ntpd.
> 
> root at genshi:~# journalctl --unit ntp
> -- Logs begin at Sun 2015-06-07 21:18:45 CEST, end at Sun 2015-06-07 21:48:29 CEST. --
> Jun 07 21:18:52 genshi.die-welt.net ntpd[648]: ntpd 4.2.6p5 at 1.2349-o Fri Apr 10 19:04:04 UTC 2015 (1)
> Jun 07 21:18:52 genshi.die-welt.net ntpd[650]: proto: precision = 0.161 usec
> Jun 07 21:18:52 genshi.die-welt.net ntp[616]: Starting NTP server: ntpd.
> 
> root at genshi:~# journalctl |grep ntp
> Jun 07 21:18:52 genshi.die-welt.net ntpd[648]: ntpd 4.2.6p5 at 1.2349-o Fri Apr 10 19:04:04 UTC 2015 (1)
> Jun 07 21:18:52 genshi.die-welt.net ntpd[650]: proto: precision = 0.161 usec
> Jun 07 21:18:52 genshi.die-welt.net ntp[616]: Starting NTP server: ntpd.
> Jun 07 21:18:53 genshi.die-welt.net ntpd[650]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING

This last line is clearly a problem.  There are at least 2
processes that try to bind() to udp port 123.

Did you try a ps to see if there is still one running?

A normal start looks like this for me (in /var/log/daemon, without
systemd):
Jun  7 23:18:54 intrepid ntpd[5142]: ntpd 4.2.6p5 at 1.2349-o Fri Apr 10 19:04:04 UTC 2015 (1)
Jun  7 23:18:54 intrepid ntpd[5143]: proto: precision = 0.120 usec
Jun  7 23:18:54 intrepid ntpd[5143]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen and drop on 1 v6wildcard :: UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen normally on 4 lo ::1 UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen normally on 5 eth0 2a02:1810:1d26:fd00:5604:a6ff:fe60:d87d UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: Listen normally on 6 eth0 fe80::5604:a6ff:fe60:d87d UDP 123
Jun  7 23:18:54 intrepid ntpd[5143]: peers refreshed
Jun  7 23:18:54 intrepid ntpd[5143]: Listening on routing socket on fd #23 for interface updates

Note that the first and second line have a different PID.  You
however seem to have at least a third PID mentioned there.

Can you try installing lockfile-progs and see if the problem goes away?


Kurt