Your message dated Tue, 18 Sep 2018 11:27:35 +0200 with message-id <[email protected]> and subject line Closing ntpdate ifupdown related bugs, removed from Buster has caused the Debian Bug report #766838, regarding ntpdate runs before network is up to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 766838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766838 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ntpdate Version: 1:4.2.6.p5+dfsg-3.1 Severity: normal Lately, ntpdate has not been correcting the clock. But when I run "ntpdate-debian" manually after the network is up, the clock is correctly adjusted. This is an excerpt from /var/log/demon.log: 4260 Oct 26 08:36:48 lenovo keyboard-setup[240]: Setting preliminary keymap...done. 4261 Oct 26 08:36:48 lenovo hdparm[277]: Setting parameters of disc: (none). 4262 Oct 26 08:36:48 lenovo networking[291]: Configuring network interfaces...done. 4263 Oct 26 08:36:48 lenovo kbd[376]: Setting console screen modes. 4264 Oct 26 08:36:48 lenovo ntpdate[371]: Can't find host ntp.uio.no: Name or service not known (-2) 4265 Oct 26 08:36:48 lenovo ntpdate[371]: Can't find host 0.debian.pool.ntp.org: Name or service not known (-2) 4266 Oct 26 08:36:48 lenovo ntpdate[371]: Can't find host 1.debian.pool.ntp.org: Name or service not known (-2) 4267 Oct 26 08:36:48 lenovo NetworkManager[1981]: <info> NetworkManager (version 0.9.10.0) is starting... 4268 Oct 26 08:36:48 lenovo NetworkManager[1981]: <info> Read config: /etc/NetworkManager/NetworkManager.conf 4269 Oct 26 08:36:48 lenovo NetworkManager[1981]: <info> WEXT support is enabled 4270 Oct 26 08:36:48 lenovo dbus[1994]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service' 4271 Oct 26 08:36:48 lenovo polkitd[2052]: started daemon version 0.105 using authority implementation `local' version `0.105' To me it seems that ntpdate is running before the network is up. This is the output of "ifconfig": eth0 Link encap:Ethernet HWaddr 3c:97:0e:bf:72:2e UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Memory:f2600000-f2620000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:80 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6304 (6.1 KiB) TX bytes:6304 (6.1 KiB) wlan0 Link encap:Ethernet HWaddr a4:4e:31:47:15:cc inet addr:192.168.0.106 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::a64e:31ff:fe47:15cc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:62758 errors:0 dropped:0 overruns:0 frame:0 TX packets:41258 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:65858238 (62.8 MiB) TX bytes:6077544 (5.7 MiB) I'm using wlan0, and have nothing connected to eth0. Best regards Torquil Sørensen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ntpdate depends on: ii dpkg 1.17.21 ii libc6 2.19-12 ii libssl1.0.0 1.0.1j-1 ii netbase 5.3 Versions of packages ntpdate recommends: pn lockfile-progs <none> ntpdate suggests no packages. -- Configuration Files: /etc/default/ntpdate changed: NTPDATE_USE_NTP_CONF=no NTPSERVERS="ntp.uio.no 0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org" NTPOPTIONS="-u" -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:4.2.8p12+dfsg-2 Dear user, the bug you have submitted is related to the ifupdown triggers shipped by the ntpdate package that did a one-shot time sync every time an interface managed by ifupdown was configured. The hooks have been removed from the ntpdate package in version 1:4.2.8p12+dfsg-2, which will be part of the Buster release. ntpdate.NEWS reads: TL;DR: The ntpdate package does NOT ship triggers for ifupdown to run a one-time sync every time an interface comes up anymore. These hooks will also be removed on upgrades to Buster. It is strongly recommended to switch to a permanent NTP daemon like ntp, systemd-timesyncd or chrony. If you need a one-time sync in your setup please arrange for it yourselves, i.e. by calling sntp with the appropriate parameters in /etc/network/interfaces(.d) . Historically the package ntpdate has included both /usr/bin/ntpdate (which is the historic go-to program for one-shot NTP querying) and ifupdown hooks to execute a one-shot NTP query on every interface up event. The ifupdown hooks have introduced buggy behaviour by syncing too often (on every ifup), too seldom (never again) and are likely to interfere with other time-keeping measures on the same system including ntpd. The hooks frequently caused dependency problems with local DNS resolvers or uncommon network configurations. They have therefor been dropped from the ntpdate package. For time synchronisation purpose please use one of the many timekeeping daemons in Debian (ntp, systemd-timesyncd, chrony). For the manual use, /usr/bin/ntpdate has been deprecated upstream and replaced by /usr/bin/sntp (in the sntp binary package). If you want a proper one-shot sync against a pool of servers you may also consider the -q option of ntpd. Best Regards, The NTP maintainers
--- End Message ---
