[Software] systemd-journald STDOUT on the console

[BossyBear]

Hi, first post.
I have a VM that I recently updated to kernel 6.1.0-0.deb11.13-amd64 and now I have systemd-journald outputing to the console even though the unit file for the service is set to null.
Messages are like...

Code: Select all

 1942.645104] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 1942.688289] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2002.776671] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2002.819103] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2062.899135] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2062.938232] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2109.050276] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2109.085003] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2123.019458] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2123.059808] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2183.138112] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2183.177249] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2243.332854] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2243.368910] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2302.554085] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2302.594133] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2362.670602] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2362.709556] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2422.788278] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2422.828602] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2482.905047] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2482.945882] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2543.049495] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2543.093660] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.

I haven't been able to find the issue and this was not happening on the previous kernel. It's just an annoyance.

Any ideas would be appreciated.
Thanks

[lindi]

What are you trying to do? Disable systemd-journald? What command did you exactly run to disable it and what did it output?

[None1975]

Hello.

Please, check this

[Aki]

Hello,

I have a VM that I recently updated to kernel 6.1.0-0.deb11.13-amd64 [..] Messages are like...

Code: Select all

[ 1942.645104] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 1942.688289] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[ 2002.776671] systemd-journald[2940]: Received client request to rotate journal, rotating.
[ 2002.819103] systemd-journald[2940]: Vacuuming done, freed 0B of archived journals from /var/log/journal/64621be06ef44a149113cc7aa3a1495b.
[..]

I haven't been able to find the issue and this was not happening on the previous kernel. It's just an annoyance.

It looks like there's a process that triggers the journal to rotate every 60 seconds. The message is echoed to the console as usual.

I suspect it's not directly caused by the kernel.

It may be useful to check for running processes and/or services.

What type of virtual machine are you running ?

[BossyBear]

This is a VitalPBX prebuit VM that I built on XCP-NG 8.2.1. The only Debian OS I have running.

I don't remember where I got the installation medai but it was likely here https://vitalpbx.com/download-virtual-machine/
Even though that is a v3 ISO and it has since self-updated to v4.

The other VMs I have are all Ubuntu 22 and one Windows 10 Pro.

On the Debian VM after 6.1 kernel...

root@pbx:~# uname -a
Linux pbx 6.1.0-0.deb11.13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64 GNU/Linux

root@pbx:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye

I have reverted to a snapshot of the VM from before the update.

root@pbx:~# uname -a
Linux pbx 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux

apt update && apt upgrade -y
All packages are up to date.

No more annoying messages on the console.

:/

[BossyBear]

Hello.

Please, check this

Thanks for that but I don't want to disable the systemd-journald service. It is running on the v5 kernel machine and it should remain running. I just want the STDOUT messages to go to null as defined in the unit file.

/var/lib/systemd/system/systemd-journald.service

Code: Select all

[Unit]
Description=Journal Service
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Requires=systemd-journald.socket
After=systemd-journald.socket systemd-journald-dev-log.socket systemd-journald-audit.socket syslog.socket
Before=sysinit.target

[Service]
DeviceAllow=char-* rw
ExecStart=/lib/systemd/systemd-journald
FileDescriptorStoreMax=4224
IPAddressDeny=any
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
OOMScoreAdjust=-250
ProtectClock=yes
Restart=always
RestartSec=0
RestrictAddressFamilies=AF_UNIX AF_NETLINK
RestrictNamespaces=yes
RestrictRealtime=yes
RestrictSUIDSGID=yes
RuntimeDirectory=systemd/journal
RuntimeDirectoryPreserve=yes
Sockets=systemd-journald.socket systemd-journald-dev-log.socket systemd-journald-audit.socket
StandardOutput=null
SystemCallArchitectures=native
SystemCallErrorNumber=EPERM
SystemCallFilter=@system-service
Type=notify
WatchdogSec=3min

StandardOutput=null

[Aki]

Hello,

This is a VitalPBX prebuit VM that I built on XCP-NG 8.2.1. The only Debian OS I have running.

Thanks for the information.

So you did not install Debian or any userspace programs: it was a preconfigured image that you simply configured and ran within a XEN VM.

I don't remember where I got the installation medai but it was likely here https://vitalpbx.com/download-virtual-machine/
Even though that is a v3 ISO and it has since self-updated to v4.

If I understand correctly, the installation updated/upgraded itself (according to the manufacturer's configuration).

Code: Select all

root@pbx:~# uname -a
Linux pbx 6.1.0-0.deb11.13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64 GNU/Linux

root@pbx:~# cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye

I have reverted to a snapshot of the VM from before the update.

Code: Select all

root@pbx:~# uname -a
Linux pbx 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux

apt update && apt upgrade -y
All packages are up to date.

No more annoying messages on the console.

When you reverted to a previous VM snapshot, you reverted everything (kernel and user space programs).

So the update/upgrade didn't just affect the kernel, but some userspace programs, did it?

You will probably need to contact manufacturer support (a forum exists) for specific configurations.

note: moving the discussion to off-topic since it is not a standard Debian installation, but a customized Debian by the involved manufaturer.