Bug#868491: marked as done (eth0 missing from /run/network/ifstate)
Your message dated Sun, 06 Aug 2017 17:17:08 + with message-idand subject line Bug#868491: fixed in chrony 3.0-4+deb9u1 has caused the Debian Bug report #868491, regarding eth0 missing from /run/network/ifstate 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 ow...@bugs.debian.org immediately.) -- 868491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chrony Version: 3.0-4 Severity: normal Dear Maintainer, After upgrading to stretch I noticed my network was not registering correctly. By this I mean that even though the network (eth0) came up and worked, it didn't have an entry in /run/network/ifstate (the ifstate file was empty). This is using ifupdown + ifplugd in a setup that worked fine on jessie and works fine now after removing chrony. It took me a while to nail down the problem, but I finally noticed this kept showing up in my log. run-parts: /etc/network/if-up.d/chrony exited with return code 1 When I put an 'exit 0' at the top of that script my networking came up fine and was added to /run/network/ifstate. So by exiting with an error that script was preventing ifup from completing the ifstate registration. I ultimately fixed this issue by removing chrony and switching to openntpd. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chrony depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii iproute2 4.9.0-1 ii libc62.24-11+deb9u1 ii libcap2 1:2.25-1 ii libedit2 3.1-20160903-3 ii libseccomp2 2.3.1-2.1 pn libtomcrypt0 ii lsb-base 9.20161125 ii ucf 3.0036 ii util-linux 2.29.2-1 chrony recommends no packages. chrony suggests no packages. --- End Message --- --- Begin Message --- Source: chrony Source-Version: 3.0-4+deb9u1 We believe that the bug you reported is fixed in the latest version of chrony, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Blut (supplier of updated chrony package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Jul 2017 17:24:44 +0200 Source: chrony Binary: chrony Architecture: source Version: 3.0-4+deb9u1 Distribution: stretch Urgency: medium Maintainer: Vincent Blut Changed-By: Vincent Blut Description: chrony - Versatile implementation of the Network Time Protocol Closes: 868491 Changes: chrony (3.0-4+deb9u1) stretch; urgency=medium . * debian/chrony.if-up: - Do not pass the “burst” command to chronyc as the script could return an error in certain situations. As a consequence, that would prevent ifupdown from writing the current state of the interfaces in /run/network/ifstate. Thanks to John Eikenberry for reporting that issue. (Closes: #868491) . * debian/chrony.ppp.ip-up: - Take the same action as for the “chrony.if-up” script as a precautionary measure. Checksums-Sha1: 308acfbbb09d686880a05fd7c8aa00523b04d3be 1833 chrony_3.0-4+deb9u1.dsc 80c35e18d167af2b37905af40562a16cf0d2ce8d 26708 chrony_3.0-4+deb9u1.debian.tar.xz Checksums-Sha256: 57d92c3e0f387a88635a21c893b96288648ce0e25f175960092dd492b99ef04b 1833 chrony_3.0-4+deb9u1.dsc 5b92a7fb832c1a159e3188b1640068f960d8d06bf3cce0a747e75a7de55c65ab 26708 chrony_3.0-4+deb9u1.debian.tar.xz Files: d21132c217260389396b1fe94fb90f8f 1833 net optional chrony_3.0-4+deb9u1.dsc 635845f2b19709731110aaeedf7a3217 26708 net optional chrony_3.0-4+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE-
Bug#868491: marked as done (eth0 missing from /run/network/ifstate)
Your message dated Thu, 20 Jul 2017 18:04:03 + with message-idand subject line Bug#868491: fixed in chrony 3.1-5 has caused the Debian Bug report #868491, regarding eth0 missing from /run/network/ifstate 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 ow...@bugs.debian.org immediately.) -- 868491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chrony Version: 3.0-4 Severity: normal Dear Maintainer, After upgrading to stretch I noticed my network was not registering correctly. By this I mean that even though the network (eth0) came up and worked, it didn't have an entry in /run/network/ifstate (the ifstate file was empty). This is using ifupdown + ifplugd in a setup that worked fine on jessie and works fine now after removing chrony. It took me a while to nail down the problem, but I finally noticed this kept showing up in my log. run-parts: /etc/network/if-up.d/chrony exited with return code 1 When I put an 'exit 0' at the top of that script my networking came up fine and was added to /run/network/ifstate. So by exiting with an error that script was preventing ifup from completing the ifstate registration. I ultimately fixed this issue by removing chrony and switching to openntpd. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chrony depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii iproute2 4.9.0-1 ii libc62.24-11+deb9u1 ii libcap2 1:2.25-1 ii libedit2 3.1-20160903-3 ii libseccomp2 2.3.1-2.1 pn libtomcrypt0 ii lsb-base 9.20161125 ii ucf 3.0036 ii util-linux 2.29.2-1 chrony recommends no packages. chrony suggests no packages. --- End Message --- --- Begin Message --- Source: chrony Source-Version: 3.1-5 We believe that the bug you reported is fixed in the latest version of chrony, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Blut (supplier of updated chrony package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Jul 2017 16:47:56 +0200 Source: chrony Binary: chrony Architecture: source Version: 3.1-5 Distribution: unstable Urgency: medium Maintainer: Vincent Blut Changed-By: Vincent Blut Description: chrony - Versatile implementation of the Network Time Protocol Closes: 868491 Changes: chrony (3.1-5) unstable; urgency=medium . * debian/chrony.if-up: - Do not pass the “burst” command to chronyc as the script could return an error in certain situations. As a consequence, that would prevent ifupdown from writing the current state of the interfaces in /run/network/ifstate. Thanks to John Eikenberry for reporting that issue. (Closes: #868491) . * debian/chrony.ppp.ip-up: - Take the same action as for the “chrony.if-up” script as a precautionary measure. Checksums-Sha1: 22f8d201a47ef977b7e9858ba4fcd4d1184fc8a2 1886 chrony_3.1-5.dsc 4b18cfbc9076a7938814f67f1fc635a1e038a42b 27260 chrony_3.1-5.debian.tar.xz Checksums-Sha256: 353c11de9e97b520249c6063cb38d129b1c356f0c0a0f1c218f13a6ebf097dac 1886 chrony_3.1-5.dsc 28cf4be25dd924e01040e837dd55a8900be549b7825bccb77ed6af4b78c5d1b5 27260 chrony_3.1-5.debian.tar.xz Files: a6e76dd0488ff24c211813ee9fcb74cf 1886 net optional chrony_3.1-5.dsc 40eba81a2341467fca227294c01fbfda 27260 net optional chrony_3.1-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAllw6zQACgkQnFyZ6wW9 dQqrKQgApjsKtyTm5hb/Q6Ty8fIqXR+CVV4SQF2joIjzfzioWbFh+HUrXprIdTbL