Bug#966612: systemd-networkd failed to restart on upgrade to 246-1
Michael Biebl
biebl at debian.org
Fri Jul 31 14:40:54 BST 2020
Control: clone -1 -2
Control: reassign -2 lintian
Control: severity -2 wishlist
Control: retitle -2 "Please if Standard{Output,Error}=syslog is used"
Hi Ansgar,
thanks for testing the v246 package from experimental.
Am 31.07.2020 um 14:45 schrieb Ansgar:
> 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 >
Looks like something we should file individual bug reports for or add a
lintian check. I decided for the latter for now.
Dear lintian maintainers, please see
https://github.com/systemd/systemd/blob/master/NEWS#L101
```
* StandardError= and StandardOutput= in unit files no longer support
the "syslog" and "syslog-console" switches. They were long removed
from the documentation, but will now result in warnings when used,
and be converted to "journal" and "journal+console" automatically.
```
Since journal is the default anyway, I guess the best recommendation is,
that maintainers simply remove any such lines from their unit files.
See also
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#StandardOutput=
> | Jul 31 14:30:06 systemd[1]: Unknown serialization item 'show-status=no', ignoring.
Interesting, I've not seen this one before. Might be worth investigating
separately what this is about if it's reproducible.
> | 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
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?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200731/e6d9e96f/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list