On Mon, Jun 08, 2015 at 09:14:09AM +0200, Evgeni Golov wrote: > Hi Kurt, > > On Sun, Jun 07, 2015 at 11:25:44PM +0200, Kurt Roeckx wrote: > > > > 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? > > Sorry, forgot to mention this in the initial report. I ran ps after > bootup and there was no ntp procs running. > > > 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? > > Yes, that helped. > > ps aoutput looks like this after boot: > root@genshi:~# ps aux |grep ntp > root 568 0.0 0.1 20072 2440 ? S 09:10 0:00 /bin/sh > /etc/network/if-up.d/ntpdate > root 570 0.0 0.0 6268 628 ? S 09:10 0:00 > lockfile-create /var/lock/ntpdate > root 622 0.0 0.1 22452 3724 ? Ss 09:10 0:00 /bin/sh > /etc/init.d/ntp start > root 663 0.0 0.0 6268 632 ? S 09:10 0:00 > lockfile-create /var/lock/ntpdate > > Could it be ntpdate which is fucking up the start of ntpd here before?
Yes, and ntpdate recommends lockfile-progs ... Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
