heftig/rtkit

log spam from rtkit-daemon

Opened this issue · 3 comments

foresto commented

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 commented

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.)

  • 👍1
jacobmcnamee commented

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

  • 👍2
  • 🎉3
  • ❤️1
BillyCroan commented

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.