Univention Bugzilla – Bug 39299
ntpd not starting at boot
Last modified: 2015-10-14 14:57:09 CEST
2015072821000011 2015082621000263 2015090121000352 We had several reports of ntpd not starting at boot time. After boot, the service can always be started via init script. One customer (2015082621000263) reported daemon.log messages like the following: Aug 25 15:24:05 gs-rtlf ntpdate[2779]: adjust time server 172.25.10.10 offset 0.000062 sec Aug 25 15:24:06 gs-rtlf ntpdate[2717]: step time server 172.25.10.10 offset 0.000302 sec Aug 25 15:24:23 gs-rtlf ntpd[4406]: ntpd 4.2.6p5@1.2349-o Fri Jun 5 11:37:07 UTC 2015 (1) Aug 25 15:24:23 gs-rtlf ntpd[4407]: proto: precision = 0.112 usec Aug 25 15:24:23 gs-rtlf ntpd[4407]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Aug 25 15:24:28 gs-rtlf ntpdate[4327]: step time server 172.25.10.10 offset 0.078534 sec There are two init-Scripts that do ntp* calls. One is "rdate" (:-)) which calls ntpdate (but with "-u" for "Direct ntpdate to use an unprivileged port for outgoing packets.") and one is "ntpd" (which starts ntpd). Another customer (2015090121000352) disabled the "rdate" calls in rdate init-Script and ntpd starts fine now. I can barely see a reason why that should help.
Additional case: 2015090821000143
univention-base-files now depends on "lockfile-progs", which is used by both /etc/init.d/ntp and /etc/network/if-up.d/ntpdate for mutual exclusion. Commit (incl 4.1): 63774 YAML (63775): 2015-09-16-univention-base-files.yaml
lockfile-progs is an unmaintained package! so if now want to use lockfile-progs, please provide the package in maintained for 4.0-3 AND 4.1-0 (at the moment the update/installation of 4.1-0 breaks because of the missing lockfile-progs packge)
Done in Bug #39357. Please announce errata updates for ntpd and lockfile-progs together!
YAML: OK Tests: OK, see also Bug #39297 which adds a test case for this issue. Code review: OK
<http://errata.software-univention.de/ucs/4.0/339.html>