Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
Am Mittwoch, 30. April 2008 schrieb Kiko Piris: On system boot, ntp init script stalls for a very long time and then prints this error (?) : Starting NTP server: ntpdlockfile creation failed Do you have ntpdate installed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
On 30/04/2008 at 11:23 +0200, Peter Eisentraut wrote: Do you have ntpdate installed? Yes, I do. -- Kiko Private mail is preferred encrypted: http://www.pirispons.net/pgpkey.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
Am Mittwoch, 30. April 2008 schrieb Kiko Piris: On 30/04/2008 at 11:23 +0200, Peter Eisentraut wrote: Do you have ntpdate installed? Yes, I do. Then ntpdate is blocking the ntp port, and ntpd has to wait for it. The new package version does it properly; older versions were somewhat broken in this respect. You could perhaps follow along and verify this if you put set -x in /etc/network/if-up.d/nptdate. But really the best solution is to uninstall ntpdate, because it is useless in this setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
On 30/04/2008 at 13:12 +0200, Peter Eisentraut wrote: Then ntpdate is blocking the ntp port, and ntpd has to wait for it. The new package version does it properly; older versions were somewhat broken in this respect. You could perhaps follow along and verify this if you put set -x in /etc/network/if-up.d/nptdate. blocking the ntp port??? As far as I can see, both /etc/network/if-up.d/ntpdate and /etc/init.d/ntp establish a lock on /var/lock/ntpdate. The second script to be run in my case is /etc/init.d/ntp and it keeps waiting on lockfile-create /var/lock/ntpdate. I can’t see anything related to ntp port. But, please, bear in mind that I’ve never used those locks and I could very well be mistaken). But really the best solution is to uninstall ntpdate, because it is useless in this setup. It’s not totally useless imho, I have a laptop that sometimes loses the hardware clock, ntpd doesn’t correct the time if there’s too much drift between the local clock and the server’s (here, ntpdate comes handy). I don’t see why those two packages should lock each other. ntpdate doesn’t keep running in the background with a socket open on ntp port or anything, ntp does do it. But as far as I can tell, the only problem related to that would be ntpdate trying to open a socket to connect to the server and beeing unable to do so because ntp has it, in that case ntpdate would simply fail). Anyway, if there’s really a conflict that I can’t see between those two packages, I think debian packaging system should reflect it. Thanks! -- Kiko Private mail is preferred encrypted: http://www.pirispons.net/pgpkey.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
Am Mittwoch, 30. April 2008 schrieb Kiko Piris: As far as I can see, both /etc/network/if-up.d/ntpdate and /etc/init.d/ntp establish a lock on /var/lock/ntpdate. The second script to be run in my case is /etc/init.d/ntp and it keeps waiting on lockfile-create /var/lock/ntpdate. I can’t see anything related to ntp port. But, please, bear in mind that I’ve never used those locks and I could very well be mistaken). Please see bug #436029 for the reasons this change was made. Anyway, if there’s really a conflict that I can’t see between those two packages, I think debian packaging system should reflect it. There is no conflict, but if you run both at the same time, one has to wait. That is what you are seeing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478655: [pkg-ntp-maintainers] Bug#478655: 'ntpdlockfile creation failed' on system boot
On 30/04/2008 at 14:04 +0200, Peter Eisentraut wrote: Please see bug #436029 for the reasons this change was made. Ok, I see. There is no conflict, but if you run both at the same time, one has to wait. That is what you are seeing. Looking it a bit closely I’ve found my problem: in /etc/network/if-up.d/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2/dev/null was failing and returning a non zero exit code, and thus lockfile-remove $LOCKFILE wasn’t executed (that script has a set -e at the beginning). That’s why ntp initscript stalled later, because of the not removed lockfile. Changing the previous line to /usr/sbin/ntpdate-debian -s $OPTS 2/dev/null || /bin/true “solves” the problem for me, but I would guess that that does not solve the race condition of bug #436029. Thanks again. -- Kiko Private mail is preferred encrypted: http://www.pirispons.net/pgpkey.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
