Control: tags -1 moreinfo On Fri, 09 Aug 2024 15:32:56 +0200 "F. Stoyan" <fstoyan+report...@swapon.de> wrote: > Package: systemd > Version: 252.29-1~deb12u1 > Severity: normal > > Dear Maintainer, > > the manual page journald.conf(5) states very clearly: > > ReadKMsg= > Takes a boolean value. If enabled systemd-journal processes /dev/kmsg > messages generated by the kernel. In the default journal namespace > this option is enabled by default, it is disabled in all others. > > But, every time a non default journal namespace is spawnd, it > complains very loudly: > > Aug 07 16:30:55 systemd[1]: Starting systemd-journald@bulk.service - Journal Service for Namespace bulk... > Aug 07 16:30:55 systemd-journald[2081]: Failed to open /dev/kmsg, ignoring: Operation not permitted > Aug 07 16:30:55 systemd[1]: Started systemd-journald@bulk.service - Journal Service for Namespace bulk. > Aug 07 16:31:25 systemd[1]: systemd-journald@bulk.service: Deactivated successfully. > > The namespace configuration is at follows: > > $ systemd-analyze cat-config systemd/journ...@bulk.conf > # /etc/systemd/journ...@bulk.conf > # Use 'systemd-analyze cat-config systemd/journ...@bulk.conf' to display the full config. > # See journald.conf(5) for details. > > [Journal] > Storage=volatile > RuntimeMaxUse=16M > ReadKMsg=no > > It does not matter whether "ReadKMsg=no" is configured or not, > it does not change the behavior.
Can you reproduce this on testing or unstable? -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
