Bug#1078331: systemd: All non-default Journal Namespaces read from /dev/kmem
Luca Boccassi
bluca at debian.org
Fri Aug 9 14:51:38 BST 2024
Control: tags -1 moreinfo
On Fri, 09 Aug 2024 15:32:56 +0200 "F. Stoyan"
<fstoyan+reportbug at 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 at 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 at bulk.service -
Journal Service for Namespace bulk.
> Aug 07 16:31:25 systemd[1]: systemd-journald at bulk.service:
Deactivated successfully.
>
> The namespace configuration is at follows:
>
> $ systemd-analyze cat-config systemd/journald at bulk.conf
> # /etc/systemd/journald at bulk.conf
> # Use 'systemd-analyze cat-config systemd/journald at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240809/07a45e2f/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list