search

heftig / rtkit

Branched from git://git.0pointer.net/rtkit
Other
47 stars 20 forks source link

rtkit-daemon: Failed to look up client #8

Closed tiiiecherle closed 5 years ago

tiiiecherle commented 5 years ago

Hey,

thanks for maintaining this project. I use archlinux with all packages up-to-date. After upgrading rtkit to 0.12 the systemd service unit itself says it starts but its internal rtkit-daemon command gives the following error.

rtkit-daemon[...]: Failed to look up client

This happens on every boot.

Downgrading to 0.11+10+g493a135-1 solves the problem.

Sorry I can not provide more information. Hope this helps to solve it. Thanks for looking into it in advance.

Kind regards

Tom

heftig commented 5 years ago

Isn't there any more to this error? It should be followed by a colon and more details.

heftig commented 5 years ago

Also, are there any failures or warnings preceding it?

tiiiecherle commented 5 years ago

Showing the log of the systemd unit since its start with this command:

unit=rtkit-daemon
ts=$(systemctl show -p ActiveEnterTimestamp $unit)
journalctl -u $unit --since "$(echo $ts | awk '{print $2 $3}')" > /media/sf_files/"$unit"_log.txt

gives me

Mär 22 15:35:25 archvbox systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Mär 22 15:35:25 archvbox systemd[1]: Started RealtimeKit Scheduling Policy Service.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Successfully called chroot.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Successfully dropped privileges.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Successfully limited resources.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Running.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Watchdog thread running.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Canary thread running.
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:25 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Supervising 0 threads of 0 processes of 1 users.
Mär 22 15:35:26 archvbox rtkit-daemon[1431]: Failed to look up client: No such file or directory
heftig commented 5 years ago

Does it work again if you add CAP_SYS_PTRACE to the CapabilityBoundingSet in /usr/lib/systemd/system/rtkit-daemon.service, then reboot?

tiiiecherle commented 5 years ago

Unfortunately still not working with the suggested entry.

heftig commented 5 years ago

Are you using hidepid?

tiiiecherle commented 5 years ago

Are you using hidepid?

Yes. The respective entry in /etc/fstab is proc /proc proc rw,nosuid,nodev,noexec,hidepid=2,gid=proc 0 0

And /etc/systemd/system/systemd-logind.service.d/hidepid.conf contains:

[Service]
SupplementaryGroups=proc
heftig commented 5 years ago

Okay, I'm moving this conversation to #9, then.

Duplicate of #9.