Bonjour à toutes et tous,
alors, j’ai un problème assez embêtant.
Mes logs deviennent enormes en quelques heures (c’est d’autant plus embêtant car il y a de l’aléatoire là dedans) et finissent par saturer la partition racine.
J’ai un Lenovo Thinkpad X1 Carbone avec Debian Bullseye, avec ce kernel
Linux debian-think 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/LinuxNaturellement, la première chose que j’ai faite est de regarder si dans ces logs syslog (qui peuvent arriver à 148Mo en une heure 
) il n’y a pas un message d’erreur recourent.
Oui, il y en a…et pleins de différents (et encore, je n’ai pas pu tout voir vu que ça fait des Go de lignes).
Ce que j’ai trouvé, répété plusieurs fois pas seconde, c’est par exemple :
mar 30 22:03:50 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:51 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:51 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:51 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:51 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:51 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
mar 30 22:03:52 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i>
J’ai en premier lieu fait quelques recherches sur iio-sensor-prox, mais je n’arrive pas trop à comprendre…il semblerait qu’il soit lié à l’oscillomètre (que j’en ai pas à ma connaissance) et que je peux le disintaller ?
@grandtoubab y a dédié une discussion :
mais à priori pour moi ce n’est pas un problème lié au démarrage…
oizuki@debian-think:~$ sudo systemctl status iio-sensor-proxy.service
[sudo] password di oizuki:
● iio-sensor-proxy.service - IIO Sensor Proxy service
Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static)
Active: active (running) since Thu 2023-03-30 10:40:27 CEST; 1 day 4h ago
Main PID: 626 (iio-sensor-prox)
Tasks: 3 (limit: 9079)
Memory: 924.0K
CPU: 28.886s
CGroup: /system.slice/iio-sensor-proxy.service
└─626 /usr/sbin/iio-sensor-proxy
mar 30 22:57:48 debian-think iio-sensor-prox[626]: Failed to read input level at /sys/devices/pci0000:00/INT33C3:00/i2c-0/i2c-CPLM3218:00/iio:dev>
(répeté plus de 20 fois en 1 seconde)
Au rallumage, par contre, il y a des secondes avec des milliers de logs !
La première partie :
mar 30 18:37:24 debian-think systemd[52897]: Reached target Exit the Session.
mar 31 12:23:25 debian-think systemd[66587]: Queued start job for default target Main User Target.
mar 31 12:23:25 debian-think systemd[66587]: Created slice User Application Slice.
mar 31 12:23:25 debian-think systemd[66587]: Reached target Paths.
mar 31 12:23:25 debian-think systemd[66587]: Reached target Timers.
mar 31 12:23:25 debian-think systemd[66587]: Starting D-Bus User Message Bus Socket.
mar 31 12:23:25 debian-think systemd[66587]: Listening on GnuPG network certificate management daemon.
mar 31 12:23:25 debian-think systemd[66587]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mar 31 12:23:25 debian-think systemd[66587]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mar 31 12:23:25 debian-think systemd[66587]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mar 31 12:23:25 debian-think systemd[66587]: Listening on GnuPG cryptographic agent and passphrase cache.
mar 31 12:23:25 debian-think systemd[66587]: Listening on Multimedia System.
mar 31 12:23:25 debian-think systemd[66587]: Listening on debconf communication socket.
mar 31 12:23:25 debian-think systemd[66587]: Listening on Sound System.
mar 31 12:23:25 debian-think systemd[66587]: Listening on REST API socket for snapd user session agent.
mar 31 12:23:25 debian-think systemd[66587]: Listening on D-Bus User Message Bus Socket.
mar 31 12:23:25 debian-think systemd[66587]: Reached target Sockets.
mar 31 12:23:25 debian-think systemd[66587]: Reached target Basic System.
mar 31 12:23:25 debian-think systemd[66587]: Started Multimedia Service.
mar 31 12:23:25 debian-think systemd[66587]: Starting Sound Service...
mar 31 12:23:25 debian-think systemd[66587]: Starting Tracker metadata extractor...
mar 31 12:23:25 debian-think systemd[66587]: Starting Tracker file system data miner...
mar 31 12:23:25 debian-think tracker-miner-f[66607]: Set scheduler policy to SCHED_IDLE
mar 31 12:23:25 debian-think tracker-miner-f[66607]: Setting priority nice level to 19
mar 31 12:23:25 debian-think systemd[66587]: Started D-Bus User Message Bus.
mar 31 12:23:25 debian-think tracker-extract[66606]: Set scheduler policy to SCHED_IDLE
mar 31 12:23:25 debian-think tracker-extract[66606]: Setting priority nice level to 19
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvf>
mar 31 12:23:25 debian-think systemd[66587]: Starting Virtual filesystem service...
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Successfully activated service 'org.gtk.vfs.Daemon'
mar 31 12:23:25 debian-think systemd[66587]: Started Virtual filesystem service.
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMoni>
mar 31 12:23:25 debian-think systemd[66587]: Starting Virtual filesystem service - disk device monitor...
mar 31 12:23:25 debian-think pipewire[66604]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name >
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
mar 31 12:23:25 debian-think systemd[66587]: Started Virtual filesystem service - disk device monitor.
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor'>
mar 31 12:23:25 debian-think systemd[66587]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
mar 31 12:23:25 debian-think dbus-daemon[66616]: [session uid=1000 pid=66616] Activating service name='org.gnome.OnlineAccounts' requested by ':1>
mar 31 12:23:25 debian-think goa-daemon[66654]: goa-daemon version 3.38.0 starting
mar 31 12:23:25 debian-think /usr/libexec/gdm-x-session[66658]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
La suite ici : syslog_completementFOU - Pastebin.com
Ici ont mon même problème : [Résolu] syslog énorme, ouverture de paramètre système fait planter (Page 2) / Autres logiciels et problèmes généraux / Forum Ubuntu-fr.org
mais c’est lié à une carte NVIDIA et ses pilotes.
Moi j’utilise la carte interne du proc (un i7 de 4e gen, avec les pilotes intel), mais il faut dire que là j’ai branché un écran exterieur en HDMI.
Le problèmes des logs a été certes très impressionnant ces dernières heures 500Mo de log en 10h, mais ça fait un moment que je remarque que /var/log prend bien trop de place, et ça m’est déjà arrivé de ne pas pouvoir démarrer à cause de ça, même sans utiliser d’écran supplémentaire.
Là il y a un bug signalé du même accabli mais sans suivi : Bug #1853328 “gdm-x-session loops printing its mode lines to sys...” : Bugs : xorg-server package : Ubuntu
Là par exemple, dans les derniers 10 minutes (, je vois des logs prendre enormement de place (plusieurs en une seconde) sur un autre problème rien à voir :
mar 31 15:46:59 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
La suite ici :
mar 31 15:47:02 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:02 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:02 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:05 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:05 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:05 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:08 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:08 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:08 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:10 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:10 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:10 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:13 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:13 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:13 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:16 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:16 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:16 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:19 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:19 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:19 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:22 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:22 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:22 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:23 debian-think rtkit-daemon[837]: Supervising 11 threads of 6 processes of 2 users.
mar 31 15:47:23 debian-think rtkit-daemon[837]: Supervising 11 threads of 6 processes of 2 users.
mar 31 15:47:24 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:24 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:26 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:26 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:28 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:28 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:28 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:31 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:31 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:31 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:34 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:34 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:34 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:37 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:37 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:37 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:39 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:41 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:41 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:41 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:43 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:43 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:43 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:46 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:46 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:46 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:49 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b0>
mar 31 15:47:49 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:49 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209af>
mar 31 15:47:52 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:52 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:52 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:55 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:55 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b1>
mar 31 15:47:55 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:57 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:57 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:47:57 debian-think nautilus[6191]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x56209b2>
mar 31 15:48:00 debian-think nautilus[6191]: Unexpected plugin res
Ce qui est du coup surprenant, c’est qu’à chaque fois il s’agit d’un message différent qui est répété plusieurs fois en une seconde.
Ne sachant pas par où commencer pour resoudre les problèmes enoncés dans les logs (vu que, selon les fois, ils sont toujours différents), j’ai donc modifié /etc/systemd/journal.conf pour éviter la saturation :
SystemMaxUse=400M
#SystemKeepFree=
SystemMaxFileSize=40M
SystemMaxFiles=100
ça vous semble raisonnable ?
Il aurait mieux valu modifier logrotate (à priori devraient avoir la même fonction…).
Merci en tout cas pour toute suggestion !