0

I noticed after each reboot I have rtkit that fails to start.

➜  ~ 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 Fri 2019-05-24 12:49:34 CEST; 5s ago
  Process: 15496 ExecStart=/usr/lib/rtkit/rtkit-daemon (code=exited, status=1/FAILURE)
 Main PID: 15496 (code=exited, status=1/FAILURE)

May 24 12:49:34 booblin rtkit-daemon[15496]: Successfully called chroot.
May 24 12:49:34 booblin rtkit-daemon[15496]: Successfully dropped privileges.
May 24 12:49:34 booblin rtkit-daemon[15496]: Successfully limited resources.
May 24 12:49:34 booblin rtkit-daemon[15496]: pthread_create failed: Resource temporarily unavailable
May 24 12:49:34 booblin rtkit-daemon[15496]: Canary thread running.
May 24 12:49:34 booblin rtkit-daemon[15496]: Exiting canary thread.
May 24 12:49:34 booblin rtkit-daemon[15496]: Demoting known real-time threads.
May 24 12:49:34 booblin rtkit-daemon[15496]: Demoted 0 threads.
May 24 12:49:34 booblin systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE
May 24 12:49:34 booblin systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'.

If I try to start it manuall after I login, it fails with the very same message: pthread_create failed

The only way I found to start it after I login in in my X session is to stop docker :

sudo systemctl stop docker.service
sudo systemctl start  rtkit-daemon.service
sudo systemctl start docker.service

is there a conflict somewhere or something I can do about it ?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.