Your message dated Sun, 2 Aug 2020 22:10:32 +0200
with message-id <[email protected]>
and subject line Re: Bug#966612: systemd-networkd failed to restart on upgrade
to 246-1
has caused the Debian Bug report #966612,
regarding systemd-networkd failed to restart on upgrade to 246-1
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.)
--
966612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966612
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 246-1
Severity: minor
systemd-networkd failed to (re)start on an upgrade from systemd
245.6-2 to 246-1:
+---
| Jul 31 14:30:06 systemd[1]: Reexecuting.
| Jul 31 14:30:06 systemd[1]: systemd 246-1 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LI>
| Jul 31 14:30:06 systemd[1]: Detected architecture x86-64.
| Jul 31 14:30:06 kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted;
see https://wiki.debian.org/SecureBoot
| Jul 31 14:30:06 systemd[1]: /lib/systemd/system/plymouth-start.service:16:
Unit configured to use KillMode=none. This is unsafe, >
| Jul 31 14:30:06 systemd[1]: /lib/systemd/system/apt-listbugs.service:30:
Standard output type syslog is obsolete, automatically u>
| Jul 31 14:30:06 systemd[1]: /lib/systemd/system/apt-listbugs.service:31:
Standard output type syslog is obsolete, automatically u>
| Jul 31 14:30:06 systemd[1]: /lib/systemd/system/gdm.service:30: Standard
output type syslog is obsolete, automatically updating t>
| Jul 31 14:30:06 systemd[1]: /lib/systemd/system/smartmontools.service:10:
Standard output type syslog is obsolete, automatically >
| Jul 31 14:30:06 systemd[1]: Unknown serialization item 'show-status=no',
ignoring.
| Jul 31 14:30:07 systemd[1]: cgroup compatibility translation between legacy
and unified hierarchy settings activated. See cgroup->
| Jul 31 14:30:07 systemd[1]: Stopping Network Service...
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Succeeded.
| Jul 31 14:30:07 systemd[1]: Stopped Network Service.
| Jul 31 14:30:07 systemd[1]: Starting Network Service...
| Jul 31 14:30:07 systemd-networkd[171450]: Could not enumerate links: Exchange
full
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Main process exited,
code=exited, status=1/FAILURE
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:07 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Scheduled restart job,
restart counter is at 1.
| Jul 31 14:30:07 systemd[1]: Stopped Network Service.
| Jul 31 14:30:07 systemd[1]: Starting Network Service...
| Jul 31 14:30:07 systemd[1]: Stopping Network Name Resolution...
| Jul 31 14:30:07 systemd[1]: systemd-resolved.service: Succeeded.
| Jul 31 14:30:07 systemd[1]: Stopped Network Name Resolution.
| Jul 31 14:30:07 systemd-networkd[171452]: Could not enumerate links: Exchange
full
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Main process exited,
code=exited, status=1/FAILURE
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:07 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Scheduled restart job,
restart counter is at 2.
| Jul 31 14:30:07 systemd[1]: Stopped Network Service.
| Jul 31 14:30:07 systemd[1]: Starting Network Service...
| Jul 31 14:30:07 systemd-networkd[171458]: Could not enumerate links: Exchange
full
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Main process exited,
code=exited, status=1/FAILURE
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:07 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:07 systemd[1]: systemd-networkd.service: Scheduled restart job,
restart counter is at 3.
| Jul 31 14:30:07 systemd[1]: Stopped Network Service.
| Jul 31 14:30:07 systemd[1]: Starting Network Service...
| Jul 31 14:30:08 systemd-networkd[171460]: Could not enumerate links: Exchange
full
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Main process exited,
code=exited, status=1/FAILURE
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:08 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Scheduled restart job,
restart counter is at 4.
| Jul 31 14:30:08 systemd[1]: Stopped Network Service.
| Jul 31 14:30:08 systemd[1]: Starting Network Service...
| Jul 31 14:30:08 systemd-networkd[171462]: Could not enumerate links: Exchange
full
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Main process exited,
code=exited, status=1/FAILURE
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:08 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Scheduled restart job,
restart counter is at 5.
| Jul 31 14:30:08 systemd[1]: Stopped Network Service.
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Start request repeated
too quickly.
| Jul 31 14:30:08 systemd[1]: systemd-networkd.service: Failed with result
'exit-code'.
| Jul 31 14:30:08 systemd[1]: Failed to start Network Service.
| Jul 31 14:30:08 systemd[1]: systemd-networkd.socket: Failed with result
'service-start-limit-hit'.
| Jul 31 14:30:08 systemd[1]: Starting Network Name Resolution...
| Jul 31 14:30:08 systemd-resolved[171463]: Positive Trust Anchors:
| Jul 31 14:30:08 systemd-resolved[171463]: . IN DS 20326 8 2
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
| Jul 31 14:30:08 systemd-resolved[171463]: Negative trust anchors:
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.>
| Jul 31 14:30:08 systemd-resolved[171463]: Using system hostname '[...]'.
| Jul 31 14:30:08 systemd[1]: Started Network Name Resolution.
| Jul 31 14:30:08 systemd[1]: Stopping Flush Journal to Persistent Storage...
| Jul 31 14:30:08 systemd[1]: systemd-journal-flush.service: Succeeded.
| Jul 31 14:30:08 systemd[1]: Stopped Flush Journal to Persistent Storage.
| Jul 31 14:30:08 systemd-journald[869]: Journal stopped
| Jul 31 14:30:09 systemd-journald[869]: Received SIGTERM from PID 1 (systemd).
| Jul 31 14:30:09 systemd[1]: Stopping Journal Service...
| Jul 31 14:30:09 systemd[1]: systemd-journald.service: Succeeded.
| Jul 31 14:30:09 systemd[1]: Stopped Journal Service.
| Jul 31 14:30:09 systemd[1]: Starting Journal Service...
| Jul 31 14:30:09 systemd-journald[171468]: Journal started
| Jul 31 14:30:09 systemd-journald[171468]: System Journal
(/var/log/journal/[...]) is 3.9G, max 4.0G, 9>
| Jul 31 14:30:09 systemd[1]: Started Journal Service.
| Jul 31 14:30:09 systemd[1]: Starting Flush Journal to Persistent Storage...
| Jul 31 14:30:09 systemd-journald[171468]: System Journal
(/var/log/journal/[...]) is 3.9G, max 4.0G, 9>
| Jul 31 14:30:09 systemd[1]: Finished Flush Journal to Persistent Storage.
| Jul 31 14:30:09 systemd[1]: Reloading.
+---
Restarting it later worked just fine:
+---
| Jul 31 14:31:22 systemd[1]: Starting Network Service...
| Jul 31 14:31:22 systemd-networkd[173153]: wg0: netdev ready
| Jul 31 14:31:22 systemd-networkd[173153]: ve-sid: Gained IPv6LL
| Jul 31 14:31:22 systemd-networkd[173153]: enp0s25: Gained IPv6LL
| Jul 31 14:31:22 systemd-networkd[173153]: Enumeration completed
| Jul 31 14:31:22 systemd[1]: Started Network Service.
| Jul 31 14:31:22 systemd-networkd[173153]: wg0: netdev exists, using existing
without changing its parameters
| Jul 31 14:31:22 systemd-networkd[173153]: ve-sid: IPv6 successfully enabled
| Jul 31 14:31:22 systemd-networkd[173153]: wg0: IPv6 successfully enabled
+---
I also had turn the wired network connection (managed by
NetworkManager) off and on again for resolved to pick up the DNS
servers again.
networkd is used to manage ve-* (for nspawn containers) and wg0
(wireguard).
Ansgar
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (300, 'buildd-unstable'), (300, 'unstable'), (1,
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-8
ii libapparmor1 2.13.4-3
ii libaudit1 1:2.8.5-3+b1
ii libblkid1 2.36-1
ii libc6 2.31-2
ii libcap2 1:2.36-1
ii libcrypt1 1:4.4.16-1
ii libcryptsetup12 2:2.3.3-1
ii libgcrypt20 1.8.6-2
ii libgnutls30 3.6.14-2+b1
ii libgpg-error0 1.38-2
ii libidn2-0 2.3.0-1
ii libip4tc2 1.8.5-2
ii libkmod2 27+20200310-2
ii liblz4-1 1.9.2-2
ii liblzma5 5.2.4-1+b1
ii libmount1 2.36-1
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.34-7
ii libseccomp2 2.4.3-1+b1
ii libselinux1 3.1-2
ii libsystemd0 246-1
ii libzstd1 1.4.5+dfsg-3
ii mount 2.36-1
ii systemd-timesyncd [time-daemon] 246-1
ii util-linux 2.36-1
Versions of packages systemd recommends:
ii dbus 1.12.20-1
Versions of packages systemd suggests:
ii policykit-1 0.113-4
ii systemd-container 246-1
Versions of packages systemd is related to:
ii dracut 050+65-1
pn initramfs-tools <none>
ii libnss-systemd 246-1
ii libpam-systemd 246-1
ii udev 245.6-2
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 31 Jul 2020 15:58:21 +0200 Ansgar <[email protected]> wrote:
> On Fri, 2020-07-31 at 15:40 +0200, Michael Biebl wrote:
> > Hm, this appears to be https://github.com/systemd/systemd/issues/16319
> >
> > I appears the offending two commits were (unfortunately) cherry-picked
> > into v245.6 and fixed in v246. Since this is supposedly a transient
> > issue and upgrades from buster should not be affected, I'm inclined to
> > close this bug report. WDYT?
>
> Fine with me if it only affects upgrades from testing and also
> considering that -networkd isn't enabled by default.
Ok, let's do that then.
Regards,
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
