Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log spam from rtkit-daemon #22

Open
foresto opened this issue Sep 30, 2020 · 3 comments
Open

log spam from rtkit-daemon #22

foresto opened this issue Sep 30, 2020 · 3 comments

Comments

@foresto
Copy link

foresto commented Sep 30, 2020

rtkit-daemon 0.12 is flooding syslog with useless messages every few seconds. Example:

Sep 30 08:29:16 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:29:16 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:29:23 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:29:23 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:36:37 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:36:37 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:36:40 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.
Sep 30 08:36:40 myhost rtkit-daemon[2200]: Supervising 4 threads of 4 processes of 2 users.

Other reports:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939615

https://bugs.launchpad.net/debian/+source/rtkit/+bug/1547589

Can someone please stop the madness?

@genterminl
Copy link

genterminl commented Nov 14, 2020

Also, it seems that all these messages are logged with UTC time, not the local time. Oddly, I did find two messages "Demoting known real-time threads." and "Demoted 0 threads" logged with local time. I only found one example of each of these (together) but have not yet looked at the code to see if I can tell why the difference in time zone.

Edit: should have added I am running Gentoo Linux with openrc, not systemd, although I don't think that should matter.\

Edit 15 Nov: It looks like the messages in local time are before rtkit drops privs. Is there any way dropping privs could mess up the timezone used by the process? (I modified syslog-ng to show timezones, and the messages which which are hours off still show my local time zone.)

@jacobmcnamee
Copy link

If you are using systemd, see https://bugs.launchpad.net/debian/+source/rtkit/+bug/1547589/comments/7:

An easy way to solve this problem is to use the LogLevelMax systemd property:

  1. As root, run systemctl edit rtkit-daemon to create a new droppin for this service.

  2. Add this to the new file:

    [Service]
    LogLevelMax=warning

  3. Restart the service: systemctl restart rtkit-daemon

jdelvare added a commit to jdelvare/rtkit that referenced this issue Apr 15, 2023
The rtkit-daemon service is a lot more verbose than other services
when it doesn't have anything to do. Stop logging the debug messages
by default to avoid flooding the system log.

This addresses issue heftig#22:
heftig#22
jdelvare added a commit to jdelvare/rtkit that referenced this issue Apr 15, 2023
The rtkit-daemon service is a lot more verbose than other services
when it doesn't have anything to do. Stop logging the debug messages
by default to avoid flooding the system log.

This addresses issue heftig#22.
KenMacD added a commit to KenMacD/nixpkgs that referenced this issue Aug 4, 2023
Pull in a patch from a cleaner upstream PR to reduce logging.

Slightly update the URLs used to download the existing patches
to make it easier to find the relevant PRs.

Re: NixOS#180102, heftig/rtkit#22
@BillyCroan
Copy link

It's bad enough that FedEx keeps calling me every day to tell me there are no packages to come pick up.

Why doesn't it work if I mask /usr/lib/systemd/system/rtkit-daemon.service with /etc/systemd/system/rtkit-daemon.service which calls /usr/local/libexec/rtkit-daemon-quiet instead of /usr/libexec/rtkit-daemon ??

x360:~# cat /usr/local/libexec/rtkit-daemon-quiet
#!/bin/bash
/usr/libexec/rtkit-daemon | grep -v -e 'Supervising 0 threads of 0 processes of 0 users' -e 'Supervising 1 threads of 1 processes of 1 users'

If my rtkit daemon is super busy, fine I'll accept that in syslog. I just don't need to know that it's not doing anything every minute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants