Package: rtkit
Version: 0.13-4
Severity: important
Dear Maintainer,
since around 1sth of July, I've experienced issues with rtkit-daemon.service
failing to start:
---
Jul 01 06:42:43 debian64 systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
Jul 01 06:42:43 debian64 systemd[1]: rtkit-daemon.service: Main process exited,
code=exited, status=1/FAILURE
Jul 01 06:42:43 debian64 systemd[1]: rtkit-daemon.service: Failed with result
'exit-code'.
Jul 01 06:42:43 debian64 systemd[1]: Failed to start RealtimeKit Scheduling
Policy Service.
[repeated every 2 - 5 seconds!]
---
I noticed this because as a result of rtkit-daemon missing, pulseaudio will
fail to start.
As a workaround I found that starting /usr/libexec/rtkit-daemon as root
manually "worked"
and pulseaudio came up as well.
I looked at the service file and added strace to it to see what's going on:
---
Jul 07 09:50:24 debian64 strace[23820]: connect(3, {sa_family=AF_UNIX,
sun_path="/run/dbus/system_bus_socket"}, 29) = -1 ECONNREFUSED (Connection
refused)
Jul 07 09:50:24 debian64 strace[23820]: close(3)
= 0
[...]
Jul 07 09:50:24 debian64 strace[23820]: socket(AF_UNIX,
SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
Jul 07 09:50:24 debian64 strace[23820]: connect(3, {sa_family=AF_UNIX,
sun_path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
Jul 07 09:50:24 debian64 strace[23820]: close(3)
= 0
Jul 07 09:50:24 debian64 strace[23820]: getpid()
= 23823
Jul 07 09:50:24 debian64 strace[23820]: socket(AF_UNIX,
SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
Jul 07 09:50:24 debian64 strace[23820]: connect(3, {sa_family=AF_UNIX,
sun_path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
Jul 07 09:50:24 debian64 strace[23820]: close(3)
= 0
Jul 07 09:50:24 debian64 strace[23820]: getpid()
= 23823
Jul 07 09:50:24 debian64 strace[23820]: socket(AF_UNIX,
SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
Jul 07 09:50:24 debian64 strace[23820]: connect(3, {sa_family=AF_UNIX,
sun_path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
Jul 07 09:50:24 debian64 strace[23820]: close(3)
= 0
Jul 07 09:50:24 debian64 strace[23820]: exit_group(1)
= ?
Jul 07 09:50:24 debian64 strace[23820]: +++ exited with 1 +++
Jul 07 09:50:24 debian64 systemd[1]: rtkit-daemon.service: Main process exited,
code=exited, status=1/FAILURE
Jul 07 09:50:24 debian64 systemd[1]: rtkit-daemon.service: Failed with result
'exit-code'.
Jul 07 09:50:24 debian64 systemd[1]: Failed to start RealtimeKit Scheduling
Policy Service.
---
So, the service had issues connecting to dbus and /dev/log which was strange
since every other
service had no issues and worked "fine". I tried playing around with adding all
the CapabilityBoundingSet I could find,
added "RestrictAddressFamilies=AF_UNIX AF_LOCAL AF_NETLINK" and
"ReadWritePaths=/dev/log"... but to no avail.
In the end I removed PrivateNetwork=yes and, reloaded and the rtkit-
daemon.service started right up without issues.
Reading up on PrivateNetwork on
<https://www.freedesktop.org/software/systemd/man/systemd.exec.html>
I found this nugget of information:
"Note that this option will disconnect all socket families from the host,
including AF_NETLINK and AF_UNIX.
Effectively, for AF_NETLINK this means that device configuration events
received from systemd-udevd.service(8)
are not delivered to the unit's processes. And for AF_UNIX this has the effect
that AF_UNIX sockets in the
abstract socket namespace of the host will become unavailable to the unit's
processes (however, those located
in the file system will continue to be accessible)."
so, it sounds like "those located in the file system will continue to be
accessible" seems to be broken.
Cheers,
Christian
PS.: This is with a 5.19-rc4 kernel, I'll try debian's 5.18.0-2-amd64 later as
well.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, powerpc, mips, arm64
Kernel: Linux 5.19.0-rc4-wt+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_DE.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages rtkit depends on:
ii adduser 3.121
ii dbus 1.14.0-1
ii libc6 2.33-7
ii libcap2 1:2.44-1
ii libdbus-1-3 1.14.0-1
ii libsystemd0 251.2-8
ii policykit-1 0.105-33
rtkit recommends no packages.
rtkit suggests no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
-- debsums errors found:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
debsums: changed file /lib/systemd/system/rtkit-daemon.service (from rtkit
package)
