Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#939615: rtkit: Flooding syslog

17 views
Skip to first unread message

Oliver Schode

unread,
Sep 6, 2019, 3:50:04 PM9/6/19
to
Package: rtkit
Version: 0.12-4
Severity: important
Tags: upstream

Hello,

beginning with the latest update, rtkit-daemon is filling my syslog with
near identical, informational messages like:

Sep 06 20:41:57 localhost rtkit-daemon[14050]: Supervising 17 threads of 9 processes of 1 users.
Sep 06 20:41:57 localhost rtkit-daemon[14050]: Supervising 17 threads of 9 processes of 1 users.
Sep 06 20:41:57 localhost rtkit-daemon[14050]: Supervising 17 threads of 9 processes of 1 users.
Sep 06 20:41:57 localhost rtkit-daemon[14050]: Supervising 17 threads of 9 processes of 1 users.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Supervising 17 threads of 9 processes of 1 users.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Successfully made thread 14634 of process 14618 owned by '1000' RT at priority 10.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Supervising 16 threads of 9 processes of 1 users.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Supervising 16 threads of 9 processes of 1 users.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Successfully made thread 14635 of process 14618 owned by '1000' RT at priority 10.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Supervising 15 threads of 8 processes of 1 users.
Sep 06 20:41:56 localhost rtkit-daemon[14050]: Supervising 15 threads of 8 processes of 1 users.
(...)

See also:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1547589

Currently, in order to stop it I too had to uninstall as there doesn't
seem to be an easy way to terminate it and rtkit-daemon apparently has
no option to disable logging or even to reduce its level.

Greetings,
Oliver

5118...@gmx.at

unread,
Oct 30, 2020, 4:50:04 PM10/30/20
to
Probably the log level can be adjusted with systemd service file with
LogLevelMax setting.

https://www.ctrl.blog/entry/systemd-log-levels.html

I can not test it at the moment because my systemd is too old and does
not support the setting.

--
Greg

Ivo Vegter

unread,
Mar 30, 2022, 6:30:03 AM3/30/22
to
rtkit cannot be silenced by changing log levels, or even by redirecting output to /dev/null. My
/etc/systemd/system/rtkit-daemon.service.d/log.conf looks like this:

[Service]
MaxLogLevel=3
StandardOutput=null
StandardError=null

...and still rtkit writes reams of junk to the system log. Since it is a required dependency of some other software I have installed (flatpak, via xdg-desktop-portal), and something (perhaps pipewire or librewolf) auto-restarts it if you stop/disable it, there is no way to escape the hell that is rtkit supervising threads.

I'm running a newly-installed Arch system, btw.

Please help.

Michal Politowski

unread,
Mar 3, 2023, 8:50:05 AM3/3/23
to
Package: rtkit
Version: 0.13-5
Followup-For: Bug #939615

I can also confirm that setting LogLevelMax=info stops the flooding.
If you don't want to override upstream by default here, then please
at least make note of it in README.Debian.
Although I would say that flooding syslog with _debug_ messages is
something that should be overriden by the distribution if necessary.


-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (450, 'experimental')
merged-usr: no
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=ga:en:pl
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rtkit depends on:
ii adduser 3.131
ii dbus [default-dbus-system-bus] 1.14.6-1
ii libc6 2.36-8
ii libcap2 1:2.66-3
ii libdbus-1-3 1.14.6-1
ii libsystemd0 252.6-1
ii policykit-1 122-3
ii polkitd 122-3

rtkit recommends no packages.

rtkit suggests no packages.

-- no debconf information

--
Michał Politowski
Talking has been known to lead to communication if practiced carelessly.
0 new messages