Your message dated Sat, 23 Jun 2018 11:08:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#850855: [rtkit] rtkit daemon fails to start
has caused the Debian Bug report #850855,
regarding Units with PrivateTmp fail when /var is a symlink
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
850855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850855
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rtkit
Version: 0.11-4
Severity: important
--- Please enter the report below this line. ---
This bug is pretty annoying because it makes pulseaudio unusable (see
#850806).
Here are the logs:
bogdan@zmeu:~$ sudo systemctl status rtkit-daemon.service
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-01-10 20:54:59 EET; 5min
ago
Main PID: 17917 (code=exited, status=203/EXEC)
ian 10 20:54:59 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Main process exited,
code=exited, status=203/EXEC
ian 10 20:54:59 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy
Service.
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed
state.
ian 10 20:54:59 zmeu systemd[1]: rtkit-daemon.service: Failed with result
'exit-code'.
bogdan@zmeu:~$ sudo systemctl start rtkit-daemon.service
Job for rtkit-daemon.service failed because the control process exited with
error code.
See "systemctl status rtkit-daemon.service" and "journalctl -xe" for details.
bogdan@zmeu:~$ sudo systemctl status rtkit-daemon.service
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-01-10 21:00:32 EET; 10s
ago
Process: 19342 ExecStart=/usr/lib/rtkit/rtkit-daemon (code=exited, status=1/
FAILURE)
Main PID: 19342 (code=exited, status=1/FAILURE)
ian 10 21:00:32 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Main process exited,
code=exited, status=1/FAILURE
ian 10 21:00:32 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy
Service.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed
state.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Failed with result
'exit-code'.
bogdan@zmeu:~$ sudo journalctl -xe
ian 10 21:00:16 zmeu systemd[1]: Reloading.
ian 10 21:00:16 zmeu systemd[1]: apt-daily.timer: Adding 5h 21min 32.698921s
random time.
ian 10 21:00:16 zmeu sudo[19309]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:23 zmeu sudo[19328]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:23 zmeu sudo[19328]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
ian 10 21:00:23 zmeu sudo[19328]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:27 zmeu sudo[19331]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/systemctl stop rtkit-daemon.service
ian 10 21:00:27 zmeu sudo[19331]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
ian 10 21:00:27 zmeu sudo[19331]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:28 zmeu sudo[19334]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:28 zmeu sudo[19334]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
ian 10 21:00:28 zmeu sudo[19334]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:32 zmeu sudo[19339]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/systemctl start rtkit-daemon.service
ian 10 21:00:32 zmeu sudo[19339]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
ian 10 21:00:32 zmeu systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
-- Subject: Unit rtkit-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit rtkit-daemon.service has begun starting up.
ian 10 21:00:32 zmeu rtkit-daemon[19342]: Failed to connect to system bus:
Failed to connect to socket /var/run/dbus/system_bus_socket: No su
ian 10 21:00:32 zmeu rtkit-daemon[19342]: Demoting known real-time threads.
ian 10 21:00:32 zmeu rtkit-daemon[19342]: Demoted 0 threads.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Main process exited,
code=exited, status=1/FAILURE
ian 10 21:00:32 zmeu systemd[1]: Failed to start RealtimeKit Scheduling Policy
Service.
-- Subject: Unit rtkit-daemon.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit rtkit-daemon.service has failed.
--
-- The result is failed.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Unit entered failed
state.
ian 10 21:00:32 zmeu systemd[1]: rtkit-daemon.service: Failed with result
'exit-code'.
ian 10 21:00:32 zmeu sudo[19339]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:43 zmeu sudo[19348]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/systemctl status rtkit-daemon.service
ian 10 21:00:43 zmeu sudo[19348]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
ian 10 21:00:43 zmeu sudo[19348]: pam_unix(sudo:session): session closed for
user root
ian 10 21:00:52 zmeu sudo[19351]: bogdan : TTY=pts/10 ; PWD=/home/bogdan ;
USER=root ; COMMAND=/bin/journalctl -xe
ian 10 21:00:52 zmeu sudo[19351]: pam_unix(sudo:session): session opened for
user root by bogdan(uid=0)
--- System information. ---
Architecture:
Kernel: Linux 4.8.0-2-amd64
Debian Release: stretch/sid
500 unstable-debug deb.debian.org
500 unstable ftp.debian.org
500 stable repo.skype.com
500 stable dl.google.com
--- Package information. ---
Depends (Version) | Installed
===========================-+-============
adduser | 3.115
libc6 (>= 2.8) |
libcap2 (>= 1:2.10) |
libdbus-1-3 (>= 1.9.14) |
Recommends (Version) | Installed
==========================-+-===========
dbus | 1.10.14-1
policykit-1 | 0.105-17
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Version: 239-1
On Mon, 6 Mar 2017 10:03:21 -0300 Felipe Sateler <[email protected]>
wrote:
> On Sun, Mar 5, 2017 at 9:01 PM, Michael Biebl <[email protected]> wrote:
> > On Fri, 20 Jan 2017 11:38:54 -0300 Felipe Sateler <[email protected]>
> > wrote:
> >> Control: tags -1 - unreproducible moreinfo
> >> Control: reassign -1 systemd
> >> Control: affects -1 rtkit
> >> Control: retitle -1 Units with PrivateTmp fail when /var is a symlink
> >> Control: severity -1 normal
> >>
> >> On 12 January 2017 at 04:46, Bogdan Vatra <[email protected]> wrote:
> >> > Hi,
> >> >
> >> > I have an update, some time ago (~1year) I run out of space on my system
> >> > partition and I decide to move /var folder to another partition and
> >> > symlink it
> >> > back to / partition. Today I just moved back my var folder and rtkit
> >> > daemon
> >> > started to work ... :)
> >>
> >> This is a bug in systemd. A related issue is
> >> https://github.com/systemd/systemd/issues/3867 , but that is
> >> supposedly fixed in 232. BogDan, do you have version 232 installed? It
> >> may be that the issue is not fully fixed yet.
> >
> > If /var is a relative symlink to say mnt/var, it seems to work fine.
> > If /var is an absolute symlink to /mnt/var, rtkit-daemon fails to start
> > (complaining about /var/run/dbus/system_bus_socket not being available).
> > Tested with 232-18.
> >
> > That all said, I'm not sure if supporting such a setup is actually worth it.
> > If you need to move /var to a separate location, ideally you make it a
> > separate mount point. If that is not possible, I would suggest you bind
> > mount the directory. This works fine.
> >
> > Felipe, do you think this is worth investigating and spending time on?
>
> If this only affects PrivateTmp when /var is a symlink, I agree it is
> a corner case not worth spending much time on. My guess was that this
> would be a bug in a more common part of the code, and that it may
> affect other mount-related settings (RootDirectory=,
> WorkingDirectory=). I haven't been able to cause similar errors with
> those settings though.
This is supposed to be fixed in v239, closing the bug report accordingly.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
