Firefox 69 et rtkit-daemon surchargent le journal

Support Debian
#1

Salut
Chaque lancement de Firefox 69 provoque cette séquence

sept. 13 18:35:17 debian rtkit-daemon[734]: Supervising 3 threads of 1 processes of 1 users.
sept. 13 18:35:17 debian rtkit-daemon[734]: Supervising 3 threads of 1 processes of 1 users.
sept. 13 18:35:17 debian rtkit-daemon[734]: Successfully made thread 12619 of process 12605 owned by '1001' RT at priority 10.
sept. 13 18:35:17 debian rtkit-daemon[734]: Supervising 4 threads of 2 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 4 threads of 2 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 4 threads of 2 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Successfully made thread 12682 of process 12657 owned by '1001' RT at priority 10.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 5 threads of 3 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 5 threads of 3 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 5 threads of 3 processes of 1 users.
sept. 13 18:35:19 debian rtkit-daemon[734]: Successfully made thread 12681 of process 12657 owned by '1001' RT at priority 10.
sept. 13 18:35:19 debian rtkit-daemon[734]: Supervising 6 threads of 3 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 6 threads of 3 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 6 threads of 3 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Successfully made thread 12734 of process 12697 owned by '1001' RT at priority 10.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 7 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 7 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 7 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Successfully made thread 12733 of process 12697 owned by '1001' RT at priority 10.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 8 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 8 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 8 threads of 4 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Successfully made thread 12751 of process 12713 owned by '1001' RT at priority 10.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 9 threads of 5 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 9 threads of 5 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 9 threads of 5 processes of 1 users.
sept. 13 18:35:20 debian rtkit-daemon[734]: Successfully made thread 12752 of process 12713 owned by '1001' RT at priority 10.
sept. 13 18:35:20 debian rtkit-daemon[734]: Supervising 10 threads of 5 processes of 1 users.
sept. 13 18:35:22 debian dbus-daemon[2763]: [session uid=1001 pid=2763] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.212' (uid=1001 pid=12766 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/")
sept. 13 18:35:23 debian dbus-daemon[2763]: [session uid=1001 pid=2763] Successfully activated service 'org.gnome.ChromeGnomeShell'

ça veut dire quoi?

#2

Extrait de la page de man de rtkitctl

Si je regarde syslog en lançant firefox, j’ai le me type de messages. Cela me semble tout à fait normal.

#3 
apt list --installed | grep rtkit

rtkit/testing,unstable,now 0.12-4 amd64  [installé]

Il y a quand même un rapport de bug sur cette version
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939615

Il y en a d’autres qui changent la priorité de log de rtkit

https://bbs.archlinux.org/viewtopic.php?id=248893
Dans Debian j’ai ajouté

/lib/systemd/system/rtkit-daemon.service.d/log.conf

[Service]
LogLevelMax=notice

systemctl daemon-reload

systemctl restart rtkit-daemon.service

Au moins le journal n’est plus pollué avec des messages “normaux”

systemctl status rtkit-daemon.service -l --no-pager
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
   Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; enabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/rtkit-daemon.service.d
           └─log.conf
   Active: active (running) since Sat 2019-09-14 08:57:53 CEST; 4min 35s ago
 Main PID: 3620 (rtkit-daemon)
    Tasks: 3 (limit: 4268)
   Memory: 752.0K
   CGroup: /system.slice/rtkit-daemon.service
           └─3620 /usr/libexec/rtkit-daemon

sept. 14 08:57:53 debian systemd[1]: Starting RealtimeKit Scheduling Policy Service...
sept. 14 08:57:53 debian systemd[1]: Started RealtimeKit Scheduling Policy Service.

A suivre

1 J'aime
#4

Merci pour ces infos. Il y a effectivement des utilisateurs qui semblent avoir des problème avec un syslog qui sature à cause de cela.

Par conter ta méthode pour modifier le service n’est pas, AMHA, très propre. Il vaut mieux utiliser :

systemctl edit rtkit-daemon.service

plutôt que de créer /modifier des fichiers sous /lib/systemd.

1 J'aime
#5

je ne modifie pas le service livré par Debian, je lui ajoute une option dans un fichier de conf spécifique, c’est tout l’avantage

C.F

Drop-In: /usr/lib/systemd/system/rtkit-daemon.service.d
           └─log.conf
1 J'aime
#6

C’est exactement ce que fait la commande que j’ai proposé :

Drop-In: /etc/systemd/system/rtkit-daemon.service.d
          └─override.conf

J’y vois au moins trois avantages par rapport à la tienne :

  • c’est la manière standard de surcharger la configuration d’un service ;
  • c’est plus rapide ;
  • la configuration est enregistrée à l’emplacement standard des configurations système, à savoir /etc et on dans /lib ou /usr/lib qui ne devrait rien contenir d’autre que les fichiers issus des paquets Debian.
#7

ok ok ok ( faut 5 caractères) :grinning: