Bug#1079622: systemd issues many warnings about syntax in its own /lib/systemd/system/systemd-*.service files

Luca Boccassi bluca at debian.org
Tue Oct 8 21:47:40 BST 2024


Control: close -1

On Sun, 25 Aug 2024 13:45:34 +0000 Ralf Bergs <Ralf+Debian at Bergs.biz>
wrote:
> Package: systemd
> Version: 252.26-1~deb12u2
> Severity: normal
> 
> Dear Maintainer,
> 
> I just upgraded from Bullseye to Bookworm, and now I'm spotting
> countless warnings from "systemd" in my logfile:
> 
> ----------- 8x -------------
> 2024-08-25T11:02:15.303178+00:00 myhost systemd[1]: Reloading.
> 2024-08-25T11:02:15.417096+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup.service:26: Invalid syntax,
ignoring: tmpfiles.extra
> 2024-08-25T11:02:15.417257+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup.service:27: Invalid syntax,
ignoring: login.motd
> 2024-08-25T11:02:15.417353+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup.service:28: Invalid syntax,
ignoring: login.issue
> 2024-08-25T11:02:15.417445+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup.service:29: Invalid syntax,
ignoring: network.hosts
> 2024-08-25T11:02:15.417533+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup.service:30: Invalid syntax,
ignoring: ssh.authorized_keys.root
> 2024-08-25T11:02:15.442472+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-clean.service:24: Invalid syntax,
ignoring: tmpfiles.extra
> 2024-08-25T11:02:15.450375+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-tmpfiles-setup-dev.service:25: Invalid
syntax, ignoring: tmpfiles.extra
> 2024-08-25T11:02:15.450945+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysusers.service:21: Unknown key name
'ConditionCredential' in section 'Unit', ignoring.
> 2024-08-25T11:02:15.451018+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysusers.service:32: Invalid syntax,
ignoring: passwd.hashed-password.root
> 2024-08-25T11:02:15.451098+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysusers.service:33: Invalid syntax,
ignoring: passwd.plaintext-password.root
> 2024-08-25T11:02:15.451190+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysusers.service:34: Invalid syntax,
ignoring: passwd.shell.root
> 2024-08-25T11:02:15.451279+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysusers.service:37: Invalid syntax,
ignoring: sysusers.extra
> 2024-08-25T11:02:15.451380+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-sysctl.service:24: Invalid syntax,
ignoring: sysctl.extra
> 2024-08-25T11:02:15.454956+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:32: Invalid syntax,
ignoring: passwd.hashed-password.root
> 2024-08-25T11:02:15.455067+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:33: Invalid syntax,
ignoring: passwd.plaintext-password.root
> 2024-08-25T11:02:15.455144+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:34: Invalid syntax,
ignoring: passwd.shell.root
> 2024-08-25T11:02:15.455217+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:35: Invalid syntax,
ignoring: firstboot.locale
> 2024-08-25T11:02:15.455317+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:36: Invalid syntax,
ignoring: firstboot.locale-messages
> 2024-08-25T11:02:15.455452+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:37: Invalid syntax,
ignoring: firstboot.keymap
> 2024-08-25T11:02:15.455567+00:00 myhost systemd[1]:
/lib/systemd/system/systemd-firstboot.service:38: Invalid syntax,
ignoring: firstboot.timezone
> ----------- 8x -------------
> 
> I didn't modify any of these files, so I can't see how I could have
caused this issue.
> 
> OTOH, when I googled this problem, I didn't encounter any other
reports from users who seem to have the very same issue.
> 
> I didn't find any existing bugs that seem to be about the same
problem, so I created this new bug.

I'm afraid I can't see any such warnings on my bookworm installation,
nor in a new VM, so it must be something to do with your specific
machine and an upgrade gone wrong or so.



More information about the Pkg-systemd-maintainers mailing list