Ubuntu-fr

bzh-utilisateur

Partition / remplie

Bonjour à tous,
hier est apparue un problème sur mon Ubuntu qu'il n'y avais pas avant (ou que je n'avais pas vu). Un notification est apparu en m’annonçant que ma partition / n'avais quasiment plus de place. Je travaillais sur mon PC depuis plusieurs heure et je n'avais alors rien installé de nouveau et pas fais de mises à jours.

Voici mon problème :

guillaume@guillaume-pc:~$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev               6,8G       0  6,8G   0% /dev
tmpfs              1,4G    1,9M  1,4G   1% /run
/dev/sdc1           46G     42G  1,4G  97% /
tmpfs              6,8G       0  6,8G   0% /dev/shm
tmpfs              5,0M    4,0K  5,0M   1% /run/lock
tmpfs              6,8G       0  6,8G   0% /sys/fs/cgroup
/dev/loop0         148M    148M     0 100% /snap/chromium/1854
/dev/loop1         148M    148M     0 100% /snap/chromium/1864
/dev/loop2         128K    128K     0 100% /snap/bare/5
/dev/loop3         165M    165M     0 100% /snap/gnome-3-28-1804/161
/dev/loop6          66M     66M     0 100% /snap/gtk-common-themes/1515
/dev/loop4          56M     56M     0 100% /snap/core18/2284
/dev/loop5         248M    248M     0 100% /snap/gnome-3-38-2004/87
/dev/loop7          62M     62M     0 100% /snap/core20/1270
/dev/loop8          66M     66M     0 100% /snap/gtk-common-themes/1519
/dev/loop14         51M     51M     0 100% /snap/snap-store/547
/dev/loop9         219M    219M     0 100% /snap/gnome-3-34-1804/77
/dev/loop11        219M    219M     0 100% /snap/gnome-3-34-1804/72
/dev/loop13         43M     43M     0 100% /snap/snapd/14066
/dev/loop10         55M     55M     0 100% /snap/snap-store/558
/dev/loop12         56M     56M     0 100% /snap/core18/2253
/dev/loop15         44M     44M     0 100% /snap/snapd/14295
/dev/loop16         62M     62M     0 100% /snap/core20/1242
/dev/sdc3           57G    3,0G   51G   6% /home
/dev/sda1          256M     73M  184M  29% /boot/efi
tmpfs              1,4G     32K  1,4G   1% /run/user/1000
guillaume@guillaume-pc:~$

J'ai donc tout d’abord utilisé des commandes tel que sudo apt autoremove et sudo apt clean afin de nettoyer le système. Mais le problème persistait. J'ai donc cru à un virus. Ayant clamav d'installé, j'ai lancé une analyse générale du système mais pas de problèmes détectés (je ne sais pas ce que vaut clamav ni si il est à jour).
J'ai fait mes petites recherches avec l'Analyseur d'utilisation de disque et il semblerait que ce soit var/log qui soit remplis.
Comme je ne sais pas comment régler ce problème, ni si je peut le régler, je me tourne vers vous.

Pour information, je suis en dual-boot avec Windows (2 disques durs séparés, un avec Windows, l'autre avec Ubuntu). Mon disque Ubuntu est partitionné de la manière suivante :
- une partition / d'environ 50 Go
- une partition snap d'environ 8 Go
- une partition /home avec le reste du disque, soit plus de 50 Go

Depuis le problème, j'ai fais des mises à jour du système.

Merci d'avance de votre aide

xubu1957

Re : Partition / remplie

Bonjour,

Montre, en te servant du Retour utilisable de commande :

snap list --all

et :

dpkg -l | grep -v ^ii

_ _ _

Montre aussi la carte wifi :

lspci -nnk | grep 0280 -A3

Dernière modification par xubu1957 (Le 18/01/2022, à 12:15)

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

FrancisFDZ

Re : Partition / remplie

Bonjour,
nettoyage "basique"

sudo apt autoremove --purge

Voir aussi la taille de /var (notamment /var/log)
Et +1 pour les installations en snap

[Edit] clamav n'est utile que si des fichiers windows transitent par un système linux installé en serveur [/Edit]

Dernière modification par FrancisFDZ (Le 18/01/2022, à 12:37)

---

-- On peut avoir des raisons de se plaindre et n'avoir pas raison de se plaindre --
[Victor Hugo]

bzh-utilisateur

Re : Partition / remplie

guillaume@guillaume-pc:~$ snap list --all
Nom                Version                     Révision  Suivi            Éditeur     Notes
bare               1.0                         5         latest/stable    canonical✓  base
chromium           97.0.4692.71                1864      latest/stable    canonical✓  -
chromium           96.0.4664.110               1854      latest/stable    canonical✓  désactivé
core18             20211028                    2253      latest/stable    canonical✓  base,désactivé
core18             20211215                    2284      latest/stable    canonical✓  base
core20             20211115                    1242      latest/stable    canonical✓  base,désactivé
core20             20211129                    1270      latest/stable    canonical✓  base
gnome-3-28-1804    3.28.0-19-g98f9e67.98f9e67  161       latest/stable    canonical✓  -
gnome-3-34-1804    0+git.3556cb3               72        latest/stable/…  canonical✓  désactivé
gnome-3-34-1804    0+git.3556cb3               77        latest/stable/…  canonical✓  -
gnome-3-38-2004    0+git.cd626d1               87        latest/stable    canonical✓  -
gtk-common-themes  0.1-52-gb92ac40             1515      latest/stable/…  canonical✓  désactivé
gtk-common-themes  0.1-59-g7bca6ae             1519      latest/stable/…  canonical✓  -
snap-store         3.38.0-64-g23c4c77          547       latest/stable/…  canonical✓  désactivé
snap-store         3.38.0-66-gbd5b8f7          558       latest/stable/…  canonical✓  -
snapd              2.53.2                      14066     latest/stable    canonical✓  snapd,désactivé
snapd              2.53.4                      14295     latest/stable    canonical✓  snapd
guillaume@guillaume-pc:~$ dpkg -l | grep -v ^ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                        Version                               Architecture Description
+++-==========================================-=====================================-============-======================================================================================================
rc  linux-image-5.11.0-40-generic              5.11.0-40.44~20.04.2                  amd64        Signed kernel image generic
rc  linux-image-5.11.0-41-generic              5.11.0-41.45~20.04.1                  amd64        Signed kernel image generic
rc  linux-image-5.11.0-44-generic              5.11.0-44.48~20.04.2                  amd64        Signed kernel image generic
rc  linux-modules-5.11.0-40-generic            5.11.0-40.44~20.04.2                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-5.11.0-41-generic            5.11.0-41.45~20.04.1                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-5.11.0-44-generic            5.11.0-44.48~20.04.2                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.11.0-38-generic      5.11.0-38.42~20.04.1                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.11.0-40-generic      5.11.0-40.44~20.04.2                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.11.0-41-generic      5.11.0-41.45~20.04.1                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.11.0-43-generic      5.11.0-43.47~20.04.2                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.11.0-44-generic      5.11.0-44.48~20.04.2                  amd64        Linux kernel extra modules for version 5.11.0 on 64 bit x86 SMP
rc  linux-modules-extra-5.4.0-90-generic       5.4.0-90.101                          amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
guillaume@guillaume-pc:~$ lspci -nnk | grep 0280 -A3
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
	Subsystem: Hewlett-Packard Company RTL8723DE 802.11b/g/n PCIe Adapter [103c:8319]
	Kernel driver in use: rtw_8723de
	Kernel modules: rtw88_8723de
guillaume@guillaume-pc:~$ sudo apt autoremove --purge
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
guillaume@guillaume-pc:~$ 

D'accord pour clamav, mais comment je fais pour augmenter la taille de mon /var/log, car je pensais qu'on ne pouvais pas modifier la taille des partitions....

inbox

Re : Partition / remplie

Salut,

Liste les fichiers contenus dans /var/log pour voir quels sont les fichiers les plus gros :

ls -la /var/log

Ensuite affiche quelques lignes du plus gros fichiers avec :

cat /var/log/**** | tail -n 50

Remplace les **** par le nom du plus gros fichier.

A+

---

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

MicP

Re : Partition / remplie

Bonjour

Pour faire afficher une liste triée par taille (du plus petit au plus "gros")

ls  -lSr  /var/log/

Pour faire s'afficher les 50 dernières lignes du fichier
dont il faudra mettre le nom à la place des ****

tail  -n 50  /var/log/****

Dernière modification par MicP (Le 18/01/2022, à 15:42)

Qid

Re : Partition / remplie

quasiment plus de place.

je rappelle que pour commencer dans ce genre de situation ce serait bien d'avoir le réflexe d'utiliser le logiciel graphique analyseur d'utilisation des disques présent par défaut sur ubuntu pour pouvoir déterminer seul ce qui prend de la place... il existe aussi un équivalent en terminal qui lui n'est pas installé par défaut : ncdu

---

"GNU/Linux c'est que du bon mais M$ Windows ce n'est pas si mal"
Référent technique Ubuntu d'un Groupe d'Utilisateur du Libre
plus d'info sur mon profil

xubu1957

Re : Partition / remplie

Pour nettoyer :

Pour supprimer tous ces fichiers de configuration devenus sans objets et marqués "rc", et uniquement ces fichiers, exécute :

dpkg -l | awk '/^rc/{print $2}' | xargs -r sudo dpkg -P

Pour info, les précisions de nany, pour la commande de nettoyage et :

snap list --all | awk '/désactivé|disabled/{print $1, $3}' | while read snapname revision; do sudo snap remove "$snapname" --revision="$revision"; done

stockée dans > |RESOLU] snap nettoyage des versions désactivées.

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

bzh-utilisateur

Re : Partition / remplie

quasiment plus de place.

je rappelle que pour commencer dans ce genre de situation ce serait bien d'avoir le réflexe d'utiliser le logiciel graphique analyseur d'utilisation des disques présent par défaut sur ubuntu pour pouvoir déterminer seul ce qui prend de la place... il existe aussi un équivalent en terminal qui lui n'est pas installé par défaut : ncdu

Je l'ai utilisé, c'est ce que j'écris plus bas dans mon premier message.

geole

Re : Partition / remplie

Bonjour
Ne pas oublier de communiquer  les erreurs du logiciel pour une éventuelle réparation

journalctl -b -p err | tail -1000 >Trace.txt && xdg-open Trace.txt

---

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

bzh-utilisateur

Re : Partition / remplie

guillaume@guillaume-pc:~$ ls  -lSr  /var/log/
total 31236524
-rw-------  1 root              root                      0 nov.  20 14:25 ubuntu-advantage.log
-rw-------  1 root              root                      0 nov.   4 12:03 ubuntu-advantage-license-check.log
-rw-rw----  1 root              utmp                      0 déc.   1 15:43 btmp.1
-rw-rw----  1 root              utmp                      0 janv.  4 07:50 btmp
-rw-r-----  1 root              adm                       0 janv.  4 07:50 apport.log
-rw-r--r--  1 root              root                    102 janv. 16 15:13 vbox-setup.log.4
-rw-r--r--  1 root              root                    102 janv. 17 13:03 vbox-setup.log.3
-rw-r--r--  1 root              root                    102 janv. 17 21:52 vbox-setup.log.2
-rw-r--r--  1 root              root                    102 janv. 18 09:00 vbox-setup.log.1
-rw-r--r--  1 root              root                    102 janv. 18 18:09 vbox-setup.log
-rw-r-----  1 root              adm                     224 juil.  4  2021 apport.log.4.gz
-rw-r--r--  1 root              root                    267 sept.  8 18:15 alternatives.log.5.gz
-rw-r--r--  1 root              root                    267 nov.  21 15:19 alternatives.log.2.gz
-rw-r-----  1 root              adm                     371 déc.  31 19:15 apport.log.1
-rw-r--r--  1 root              root                    413 janv. 15 19:46 alternatives.log
-rw-r--r--  1 root              root                    484 déc.  27 18:39 alternatives.log.1
-rw-------  1 root              root                    522 nov.  30 18:31 ubuntu-advantage-timer.log.2.gz
-rw-r-----  1 root              adm                     569 oct.  16 12:55 apport.log.3.gz
-rw-r--r--  1 root              root                    709 sept. 18 15:34 alternatives.log.4.gz
-rw-------  1 root              root                    848 oct.   2 18:54 ubuntu-advantage.log.2.gz
-rw-r-----  1 root              adm                     902 nov.   8 20:00 apport.log.2.gz
-rw-r--r--  1 root              root                   1121 nov.  15 17:47 alternatives.log.3.gz
-rw-------  1 root              root                   1474 août   9 15:18 ubuntu-advantage.log.4.gz
-rw-------  1 root              root                   1479 sept. 14 21:38 ubuntu-advantage.log.3.gz
-rw-r--r--  1 root              root                   1501 janv. 18 18:07 gpu-manager.log
-rw-------  1 root              root                   2358 janv. 18 09:43 ubuntu-advantage-timer.log
-rw-r--r--  1 root              root                   2822 sept. 18 15:34 dpkg.log.4.gz
-rw-r--r--  1 root              root                   2934 août   5 19:24 alternatives.log.6.gz
drwxr-x---  2 root              adm                    4096 janv.  4 07:51 unattended-upgrades
drwx------  2 speech-dispatcher root                   4096 janv. 19  2020 speech-dispatcher
drwx------  2 root              root                   4096 févr.  9  2021 private
drwxr-xr-x  2 root              root                   4096 sept.  5  2019 openvpn
drwxr-sr-x+ 3 root              systemd-journal        4096 juin  13  2021 journal
drwxr-xr-x  3 root              root                   4096 juin  13  2021 installer
drwxr-xr-x  3 root              root                   4096 févr.  9  2021 hp
drwx--x--x  2 root              gdm                    4096 nov.  10  2020 gdm3
drwxr-xr-x  2 root              root                   4096 janv. 19  2021 dist-upgrade
drwxr-xr-x  2 root              root                   4096 janv.  8 09:51 cups
drwxr-xr-x  2 clamav            clamav                 4096 janv.  4 07:50 clamav
drwxr-xr-x  2 root              root                   4096 janv. 17 21:39 apt
-rw-------  1 root              root                   4402 janv.  3 19:10 ubuntu-advantage-timer.log.1
-rw-r--r--  1 root              root                   4860 nov.  30 18:44 dpkg.log.2.gz
-rw-r-----  1 syslog            adm                    5267 déc.   1 15:45 auth.log.2.gz
-rw-r-----  1 syslog            adm                    5338 oct.  16 09:05 auth.log.4.gz
-rw-r--r--  1 root              root                   5645 sept.  9 18:40 dpkg.log.5.gz
-rw-r--r--  1 root              root                  11125 déc.   7 07:23 fontconfig.log
-rw-------  1 root              root                  12461 oct.  19 08:10 boot.log.6
-rw-r--r--  1 root              adm                   22556 janv. 17 21:52 dmesg.1.gz
-rw-r--r--  1 root              root                  22608 nov.  15 18:23 dpkg.log.3.gz
-rw-r--r--  1 root              adm                   22908 janv. 16 15:12 dmesg.3.gz
-rw-r--r--  1 root              adm                   22944 janv. 17 13:03 dmesg.2.gz
-rw-r--r--  1 root              adm                   23070 janv. 15 16:15 dmesg.4.gz
-rw-r-----  1 syslog            adm                   23351 nov.  20 14:24 auth.log.3.gz
-rw-------  1 root              root                  31872 nov.   4 09:18 ubuntu-advantage.log.1
-rw-r--r--  1 root              root                  32032 oct.  16 22:26 faillog
-rw-r-----  1 syslog            adm                   64066 oct.  19 08:10 syslog.5.gz
-rw-r--r--  1 root              root                  69788 janv. 17 21:39 dpkg.log
-rw-------  1 root              root                  76030 oct.  18 18:17 boot.log.7
-rw-------  1 root              root                  76610 déc.   1 15:43 boot.log.3
-rw-------  1 root              root                  89278 nov.  24 15:45 boot.log.4
-rw-r--r--  1 root              adm                   89598 janv. 18 18:08 dmesg
-rw-r--r--  1 root              adm                   89659 janv. 18 08:59 dmesg.0
-rw-------  1 root              root                  89904 janv.  8 09:51 boot.log.1
-rw-r--r--  1 root              root                 104003 févr.  9  2021 bootstrap.log
-rw-r--r--  1 root              root                 117516 août   5 19:37 dpkg.log.6.gz
-rw-r--r--  1 root              root                 123656 déc.  29 18:05 dpkg.log.1
-rw-r-----  1 syslog            adm                  130161 janv. 18 18:26 auth.log
-rw-r-----  1 syslog            adm                  200772 janv.  4 07:51 auth.log.1
-rw-------  1 root              root                 214126 janv. 18 18:08 boot.log
-rw-r-----  1 syslog            adm                  290049 déc.   1 15:45 kern.log.2.gz
-rw-rw-r--  1 root              utmp                 292292 oct.  16 22:26 lastlog
-rw-rw-r--  1 root              utmp                 364416 janv. 18 18:12 wtmp
-rw-r-----  1 syslog            adm                  390953 oct.  16 09:05 kern.log.4.gz
-rw-------  1 root              root                 500324 janv.  4 07:50 boot.log.2
-rw-------  1 root              root                 503740 nov.  20 14:24 boot.log.5
-rw-r-----  1 syslog            adm                  535848 oct.  18 18:18 syslog.6.gz
-rw-r-----  1 syslog            adm                 1017600 oct.  16 09:05 syslog.7.gz
-rw-r-----  1 syslog            adm                 1394329 nov.  20 14:25 kern.log.3.gz
-rw-r-----  1 syslog            adm                 3648279 janv. 18 18:26 kern.log
-rw-r-----  1 syslog            adm                 5837257 janv.  4 07:50 kern.log.1
-rw-r-----  1 syslog            adm                 6645538 déc.   1 15:45 syslog.2.gz
-rw-r-----  1 syslog            adm                 7347096 nov.  24 15:50 syslog.3.gz
-rw-r-----  1 syslog            adm                41239335 nov.  20 14:24 syslog.4.gz
-rw-r-----  1 syslog            adm                57147392 janv.  8 09:59 syslog.1.gz
-rw-r-----  1 syslog            adm             15511014954 janv. 18 18:29 syslog
-rw-r-----  1 syslog            adm             16346181717 janv.  4 07:51 syslog.1
guillaume@guillaume-pc:~$ tail  -n 50  /var/log/syslog.1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] online
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Cannot reach: https://daisy.ubuntu.com
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] offline
Jan  4 07:51:24 guillaume-pc whoopsie[1412]: [07:51:24] online
Jan  4 07:51:26 guillaume-pc systemd-timesyncd[1075]: Initial synchronization to time server [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com).
Jan  4 07:51:27 guillaume-pc systemd[1]: udisks2.service: start operation timed out. Terminating.
Jan  4 07:51:28 guillaume-pc snapd[1144]: stateengine.go:149: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Jan  4 07:51:28 guillaume-pc dbus-daemon[1114]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.18' (uid=0 pid=1144 comm="/usr/lib/snapd/snapd " label="unconfined")
Jan  4 07:51:28 guillaume-pc systemd[1]: Starting Time & Date Service...
Jan  4 07:51:28 guillaume-pc dbus-daemon[1114]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jan  4 07:51:28 guillaume-pc systemd[1]: Started Time & Date Service.
Jan  4 07:51:30 guillaume-pc NetworkManager[1115]: <info>  [1641279090.6519] modem-manager: ModemManager not available
Jan  4 07:51:30 guillaume-pc systemd[1]: Started Modem Manager.
Jan  4 07:51:30 guillaume-pc NetworkManager[1115]: <info>  [1641279090.6766] modem-manager: ModemManager now available
Jan  4 07:51:32 guillaume-pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan  4 07:51:33 guillaume-pc ModemManager[1352]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.6/0000:01:00.0': not supported by any plugin
Jan  4 07:51:33 guillaume-pc ModemManager[1352]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.7/0000:02:00.0': not supported by any plugin
Jan  4 07:51:46 guillaume-pc systemd[1]: dmesg.service: Succeeded.
Jan  4 07:51:50 guillaume-pc systemd[1]: Created slice User Slice of UID 125.
Jan  4 07:51:50 guillaume-pc systemd[1]: Starting User Runtime Directory /run/user/125...
Jan  4 07:51:50 guillaume-pc systemd[1]: Finished User Runtime Directory /run/user/125.
Jan  4 07:51:50 guillaume-pc systemd[1]: Starting User Manager for UID 125...
Jan  4 07:51:51 guillaume-pc udisksd[1150]: udisks daemon version 2.8.4 exiting
Jan  4 07:51:51 guillaume-pc systemd[1]: udisks2.service: Failed with result 'timeout'.
Jan  4 07:51:51 guillaume-pc systemd[1]: Failed to start Disk Manager.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Started Pending report trigger for Ubuntu Report.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Paths.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Timers.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting D-Bus User Message Bus Socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG network certificate management daemon.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on debconf communication socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on Sound System.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on REST API socket for snapd user session agent.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on D-Bus User Message Bus Socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Sockets.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Basic System.
Jan  4 07:51:51 guillaume-pc systemd[1]: Started User Manager for UID 125.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Sound Service...
Jan  4 07:51:51 guillaume-pc systemd[1]: Started Session c1 of user gdm.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Tracker metadata extractor...
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Tracker file system data miner...
Jan  4 07:51:51 guillaume-pc systemd[1494]: Started D-Bus User Message Bus.
Jan  4 07:51:52 guillaume-pc dbus-daemon[1114]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=125 pid=1527 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Jan  4 07:51:52 guillaume-pc systemd[1]: Starting RealtimeKit Scheduling Policy Service...
guillaume@guillaume-pc:~$

Et voici Trace.txt :

-- Logs begin at Tue 2022-01-18 11:41:29 CET, end at Tue 2022-01-18 18:31:24 CET. --
janv. 18 18:07:17 guillaume-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20210331/dswload2-162)
janv. 18 18:07:17 guillaume-pc kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210331/psobject-220)
janv. 18 18:07:17 guillaume-pc systemd-modules-load[331]: Failed to insert module 'vboxdrv': Operation not permitted
janv. 18 18:07:17 guillaume-pc systemd[1]: Failed to start Load Kernel Modules.
janv. 18 18:07:23 guillaume-pc systemd-modules-load[650]: Failed to insert module 'vboxdrv': Operation not permitted
janv. 18 18:07:23 guillaume-pc systemd[1]: Failed to start Load Kernel Modules.
janv. 18 18:07:24 guillaume-pc systemd-modules-load[664]: Failed to insert module 'vboxdrv': Operation not permitted
janv. 18 18:07:24 guillaume-pc systemd[1]: Failed to start Load Kernel Modules.
janv. 18 18:07:25 guillaume-pc systemd-modules-load[667]: Failed to insert module 'vboxdrv': Operation not permitted
janv. 18 18:07:25 guillaume-pc systemd[1]: Failed to start Load Kernel Modules.
janv. 18 18:07:25 guillaume-pc systemd-backlight[708]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
janv. 18 18:07:25 guillaume-pc systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
janv. 18 18:07:25 guillaume-pc systemd-backlight[709]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address
janv. 18 18:07:25 guillaume-pc systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
janv. 18 18:09:23 guillaume-pc gdm-password][3608]: gkr-pam: unable to locate daemon control file
janv. 18 18:12:34 guillaume-pc systemd[1]: Failed to start VirtualBox Linux kernel module.

inbox

Re : Partition / remplie

Peux-tu donner le retour plus gros du contenu de syslog.1 avec :

tail  -n 500  /var/log/syslog.1

---

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

bzh-utilisateur

Re : Partition / remplie

guillaume@guillaume-pc:~$ tail  -n 200 /var/log/syslog.1
Jan  4 07:50:50 guillaume-pc NetworkManager[1115]: <info>  [1641279050.2299] device (lo): carrier: link connected
Jan  4 07:50:50 guillaume-pc NetworkManager[1115]: <info>  [1641279050.2304] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan  4 07:50:50 guillaume-pc NetworkManager[1115]: <info>  [1641279050.2324] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jan  4 07:50:50 guillaume-pc NetworkManager[1115]: <info>  [1641279050.2349] settings: (eno1): created default wired connection 'Connexion filaire 1'
Jan  4 07:50:50 guillaume-pc NetworkManager[1115]: <info>  [1641279050.2354] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan  4 07:50:51 guillaume-pc systemd[1]: kerneloops.service: Found left-over process 1414 (kerneloops) in control group while starting unit. Ignoring.
Jan  4 07:50:51 guillaume-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan  4 07:50:51 guillaume-pc systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Jan  4 07:50:51 guillaume-pc kernel: [   83.115516] Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
Jan  4 07:50:51 guillaume-pc NetworkManager[1115]: <info>  [1641279051.8873] device (wlp2s0): driver supports Access Point (AP) mode
Jan  4 07:50:51 guillaume-pc NetworkManager[1115]: <info>  [1641279051.8880] manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jan  4 07:50:51 guillaume-pc kernel: [   83.315674] r8169 0000:01:00.0 eno1: Link is Down
Jan  4 07:50:51 guillaume-pc NetworkManager[1115]: <info>  [1641279051.8894] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan  4 07:50:52 guillaume-pc kernel: [   83.468506] rtw_8723de 0000:02:00.0: start vif 70:66:55:ea:e6:f7 on port 0
Jan  4 07:50:52 guillaume-pc udisksd[1150]: Failed to load the 'mdraid' libblockdev plugin
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <warn>  [1641279053.5907] Error: failed to open /run/network/ifstate
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <info>  [1641279053.5997] supplicant: wpa_supplicant running
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <info>  [1641279053.5998] device (wlp2s0): supplicant interface state: init -> starting
Jan  4 07:50:53 guillaume-pc wpa_supplicant[1154]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <info>  [1641279053.6697] sup-iface[0x55c1be27a900,wlp2s0]: supports 4 scan SSIDs
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <info>  [1641279053.6708] device (wlp2s0): supplicant interface state: starting -> ready
Jan  4 07:50:53 guillaume-pc NetworkManager[1115]: <info>  [1641279053.6709] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan  4 07:50:54 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9601] policy: auto-activating connection 'Livebox-80E0' (4cc26026-c825-4bb6-84b7-9caa4a70b175)
Jan  4 07:50:54 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9611] device (wlp2s0): Activation: starting connection 'Livebox-80E0' (4cc26026-c825-4bb6-84b7-9caa4a70b175)
Jan  4 07:50:54 guillaume-pc kernel: [   86.404286] wlp2s0: authenticate with d4:f8:29:6d:80:e0
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9613] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:55 guillaume-pc wpa_supplicant[1154]: wlp2s0: SME: Trying to authenticate with d4:f8:29:6d:80:e0 (SSID='Livebox-80E0' freq=2462 MHz)
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9618] manager: NetworkManager state is now CONNECTING
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9624] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9628] device (wlp2s0): Activation: (wifi) access point 'Livebox-80E0' has security, but secrets are required.
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9628] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9631] sup-iface[0x55c1be27a900,wlp2s0]: wps: type pbc start...
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9661] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9664] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] device (wlp2s0): Activation: (wifi) connection 'Livebox-80E0' has security, and secrets exist.  No new secrets needed.
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'ssid' value 'Livebox-80E0'
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'scan_ssid' value '1'
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'auth_alg' value 'OPEN'
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279054.9666] Config: added 'psk' value '<hidden>'
Jan  4 07:50:55 guillaume-pc kernel: [   86.665590] wlp2s0: send auth to d4:f8:29:6d:80:e0 (try 1/3)
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279055.2355] device (wlp2s0): supplicant interface state: ready -> authenticating
Jan  4 07:50:55 guillaume-pc wpa_supplicant[1154]: wlp2s0: Trying to associate with d4:f8:29:6d:80:e0 (SSID='Livebox-80E0' freq=2462 MHz)
Jan  4 07:50:55 guillaume-pc kernel: [   86.667219] wlp2s0: authenticated
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279055.2371] device (wlp2s0): supplicant interface state: authenticating -> associating
Jan  4 07:50:55 guillaume-pc kernel: [   86.671493] wlp2s0: associate with d4:f8:29:6d:80:e0 (try 1/3)
Jan  4 07:50:55 guillaume-pc wpa_supplicant[1154]: wlp2s0: Associated with d4:f8:29:6d:80:e0
Jan  4 07:50:55 guillaume-pc wpa_supplicant[1154]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan  4 07:50:55 guillaume-pc wpa_supplicant[1154]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jan  4 07:50:55 guillaume-pc kernel: [   86.676165] wlp2s0: RX AssocResp from d4:f8:29:6d:80:e0 (capab=0x1411 status=0 aid=1)
Jan  4 07:50:55 guillaume-pc kernel: [   86.676188] rtw_8723de 0000:02:00.0: sta d4:f8:29:6d:80:e0 joined with macid 0
Jan  4 07:50:55 guillaume-pc kernel: [   86.676446] wlp2s0: associated
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279055.2515] device (wlp2s0): supplicant interface state: associating -> associated
Jan  4 07:50:55 guillaume-pc kernel: [   86.714621] wlp2s0: Limiting TX power to 20 (20 - 0) dBm as advertised by d4:f8:29:6d:80:e0
Jan  4 07:50:55 guillaume-pc NetworkManager[1115]: <info>  [1641279055.8139] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Jan  4 07:50:57 guillaume-pc wpa_supplicant[1154]: wlp2s0: WPA: Key negotiation completed with d4:f8:29:6d:80:e0 [PTK=CCMP GTK=CCMP]
Jan  4 07:50:57 guillaume-pc wpa_supplicant[1154]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to d4:f8:29:6d:80:e0 completed [id=0 id_str=]
Jan  4 07:50:57 guillaume-pc wpa_supplicant[1154]: wlp2s0: CTRL-EVENT-BEACON-LOSS 
Jan  4 07:50:57 guillaume-pc kernel: [   89.315944] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Jan  4 07:50:57 guillaume-pc NetworkManager[1115]: <info>  [1641279057.8904] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Jan  4 07:50:57 guillaume-pc NetworkManager[1115]: <info>  [1641279057.8905] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Livebox-80E0"
Jan  4 07:50:57 guillaume-pc NetworkManager[1115]: <info>  [1641279057.8907] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan  4 07:50:57 guillaume-pc NetworkManager[1115]: <info>  [1641279057.8914] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan  4 07:50:57 guillaume-pc whoopsie[1412]: [07:50:57] Using lock path: /var/lock/whoopsie/lock
Jan  4 07:50:57 guillaume-pc wpa_supplicant[1154]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-40 noise=9999 txrate=39000
Jan  4 07:50:59 guillaume-pc avahi-daemon[1110]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::9c24:bce2:5140:390a.
Jan  4 07:50:59 guillaume-pc avahi-daemon[1110]: New relevant interface wlp2s0.IPv6 for mDNS.
Jan  4 07:50:59 guillaume-pc freshclam[1408]: WARNING: Ignoring deprecated option SafeBrowsing at /etc/clamav/freshclam.conf:22
Jan  4 07:50:59 guillaume-pc avahi-daemon[1110]: Registering new address record for fe80::9c24:bce2:5140:390a on wlp2s0.*.
Jan  4 07:50:59 guillaume-pc whoopsie[1412]: [07:50:59] offline
Jan  4 07:51:00 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:00 2022 -> ClamAV update process started at Tue Jan  4 07:51:00 2022
Jan  4 07:51:00 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:00 2022 -> ^Can't query current.cvd.clamav.net
Jan  4 07:51:00 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:00 2022 -> ^Invalid DNS reply. Falling back to HTTP mode.
Jan  4 07:51:00 guillaume-pc networkd-dispatcher[1439]: WARNING: systemd-networkd is not running, output will be incomplete.
Jan  4 07:51:01 guillaume-pc systemd[1]: Started Dispatcher daemon for systemd-networkd.
Jan  4 07:51:02 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:02 2022 -> Trying to retrieve CVD header from https://database.clamav.net/daily.cvd
Jan  4 07:51:02 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:02 2022 -> ^remote_cvdhead: Download failed (6) Tue Jan  4 07:51:02 2022 -> ^ Message: Couldn't resolve host name
Jan  4 07:51:02 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:02 2022 -> ^Failed to get daily database version information from server: https://database.clamav.net
Jan  4 07:51:02 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:02 2022 -> !check_for_new_database_version: Failed to find daily database using server https://database.clamav.net.
Jan  4 07:51:02 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:02 2022 -> Trying again in 5 secs...
Jan  4 07:51:07 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:07 2022 -> Trying to retrieve CVD header from https://database.clamav.net/daily.cvd
Jan  4 07:51:07 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:07 2022 -> ^remote_cvdhead: Download failed (6) Tue Jan  4 07:51:07 2022 -> ^ Message: Couldn't resolve host name
Jan  4 07:51:07 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:07 2022 -> ^Failed to get daily database version information from server: https://database.clamav.net
Jan  4 07:51:07 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:07 2022 -> !check_for_new_database_version: Failed to find daily database using server https://database.clamav.net.
Jan  4 07:51:07 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:07 2022 -> Trying again in 5 secs...
Jan  4 07:51:08 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1347] dhcp4 (wlp2s0): option dhcp_lease_time      => '86400'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1348] dhcp4 (wlp2s0): option domain_name          => 'home'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.12.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1348] dhcp4 (wlp2s0): option domain_name_servers  => '192.168.1.1'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: New relevant interface wlp2s0.IPv4 for mDNS.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option expiry               => '1641365459'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Registering new address record for 192.168.1.12 on wlp2s0.IPv4.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option ip_address           => '192.168.1.12'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::9c24:bce2:5140:390a.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option next_server          => '192.168.1.1'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2a01:cb08:8174:1e00:b149:b8c0:6779:8212.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option requested_broadcast_address => '1'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Registering new address record for 2a01:cb08:8174:1e00:b149:b8c0:6779:8212 on wlp2s0.*.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option requested_domain_name => '1'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Withdrawing address record for fe80::9c24:bce2:5140:390a on wlp2s0.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option requested_domain_name_servers => '1'
Jan  4 07:51:10 guillaume-pc avahi-daemon[1110]: Registering new address record for 2a01:cb08:8174:1e00:a7f5:16dd:d46e:1d75 on wlp2s0.*.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1349] dhcp4 (wlp2s0): option requested_domain_search => '1'
Jan  4 07:51:10 guillaume-pc nm-dispatcher: exiting but there are still 1 requests pending
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_host_name  => '1'
Jan  4 07:51:10 guillaume-pc dbus-daemon[1114]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=1115 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_interface_mtu => '1'
Jan  4 07:51:10 guillaume-pc dbus-daemon[1114]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_ms_classless_static_routes => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_nis_domain => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_nis_servers => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_ntp_servers => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_rfc3442_classless_static_routes => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1350] dhcp4 (wlp2s0): option requested_root_path  => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option requested_routers    => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option requested_static_routes => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option requested_subnet_mask => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option requested_time_offset => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option requested_wpad       => '1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option routers              => '192.168.1.1'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1351] dhcp4 (wlp2s0): option subnet_mask          => '255.255.255.0'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1352] dhcp4 (wlp2s0): state changed unknown -> bound
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1376] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1433] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1581] dhcp6 (wlp2s0): option dhcp6_domain_search  => 'home'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1582] dhcp6 (wlp2s0): option dhcp6_name_servers   => 'fe80::d6f8:29ff:fe6d:80e0'
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279068.1582] dhcp6 (wlp2s0): state changed unknown -> bound
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3667] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3673] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3682] manager: NetworkManager state is now CONNECTED_LOCAL
Jan  4 07:51:10 guillaume-pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3714] manager: NetworkManager state is now CONNECTED_SITE
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3717] policy: set 'Livebox-80E0' (wlp2s0) as default for IPv4 routing and DNS
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3721] policy: set 'Livebox-80E0' (wlp2s0) as default for IPv6 routing and DNS
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3730] device (wlp2s0): Activation: successful, device activated.
Jan  4 07:51:10 guillaume-pc NetworkManager[1115]: <info>  [1641279070.3746] manager: startup complete
Jan  4 07:51:10 guillaume-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan  4 07:51:10 guillaume-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan  4 07:51:10 guillaume-pc systemd[1]: systemd-hostnamed.service: Succeeded.
Jan  4 07:51:12 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:12 2022 -> Trying to retrieve CVD header from https://database.clamav.net/daily.cvd
Jan  4 07:51:12 guillaume-pc systemd[1]: systemd-timedated.service: Succeeded.
Jan  4 07:51:13 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:13 2022 -> daily.cld database is up-to-date (version: 26411, sigs: 1968299, f-level: 90, builder: raynman)
Jan  4 07:51:15 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:15 2022 -> Trying to retrieve CVD header from https://database.clamav.net/main.cvd
Jan  4 07:51:15 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:15 2022 -> main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
Jan  4 07:51:17 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:17 2022 -> Trying to retrieve CVD header from https://database.clamav.net/bytecode.cvd
Jan  4 07:51:17 guillaume-pc freshclam[1408]: Tue Jan  4 07:51:17 2022 -> bytecode.cvd database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2)
Jan  4 07:51:18 guillaume-pc systemd-resolved[1074]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
Jan  4 07:51:19 guillaume-pc NetworkManager[1115]: <info>  [1641279079.4530] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] online
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] Cannot reach: https://daisy.ubuntu.com
Jan  4 07:51:23 guillaume-pc whoopsie[1412]: [07:51:23] offline
Jan  4 07:51:24 guillaume-pc whoopsie[1412]: [07:51:24] online
Jan  4 07:51:26 guillaume-pc systemd-timesyncd[1075]: Initial synchronization to time server [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com).
Jan  4 07:51:27 guillaume-pc systemd[1]: udisks2.service: start operation timed out. Terminating.
Jan  4 07:51:28 guillaume-pc snapd[1144]: stateengine.go:149: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Jan  4 07:51:28 guillaume-pc dbus-daemon[1114]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.18' (uid=0 pid=1144 comm="/usr/lib/snapd/snapd " label="unconfined")
Jan  4 07:51:28 guillaume-pc systemd[1]: Starting Time & Date Service...
Jan  4 07:51:28 guillaume-pc dbus-daemon[1114]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jan  4 07:51:28 guillaume-pc systemd[1]: Started Time & Date Service.
Jan  4 07:51:30 guillaume-pc NetworkManager[1115]: <info>  [1641279090.6519] modem-manager: ModemManager not available
Jan  4 07:51:30 guillaume-pc systemd[1]: Started Modem Manager.
Jan  4 07:51:30 guillaume-pc NetworkManager[1115]: <info>  [1641279090.6766] modem-manager: ModemManager now available
Jan  4 07:51:32 guillaume-pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan  4 07:51:33 guillaume-pc ModemManager[1352]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.6/0000:01:00.0': not supported by any plugin
Jan  4 07:51:33 guillaume-pc ModemManager[1352]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.7/0000:02:00.0': not supported by any plugin
Jan  4 07:51:46 guillaume-pc systemd[1]: dmesg.service: Succeeded.
Jan  4 07:51:50 guillaume-pc systemd[1]: Created slice User Slice of UID 125.
Jan  4 07:51:50 guillaume-pc systemd[1]: Starting User Runtime Directory /run/user/125...
Jan  4 07:51:50 guillaume-pc systemd[1]: Finished User Runtime Directory /run/user/125.
Jan  4 07:51:50 guillaume-pc systemd[1]: Starting User Manager for UID 125...
Jan  4 07:51:51 guillaume-pc udisksd[1150]: udisks daemon version 2.8.4 exiting
Jan  4 07:51:51 guillaume-pc systemd[1]: udisks2.service: Failed with result 'timeout'.
Jan  4 07:51:51 guillaume-pc systemd[1]: Failed to start Disk Manager.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Started Pending report trigger for Ubuntu Report.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Paths.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Timers.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting D-Bus User Message Bus Socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG network certificate management daemon.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on debconf communication socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on Sound System.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on REST API socket for snapd user session agent.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Listening on D-Bus User Message Bus Socket.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Sockets.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Reached target Basic System.
Jan  4 07:51:51 guillaume-pc systemd[1]: Started User Manager for UID 125.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Sound Service...
Jan  4 07:51:51 guillaume-pc systemd[1]: Started Session c1 of user gdm.
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Tracker metadata extractor...
Jan  4 07:51:51 guillaume-pc systemd[1494]: Starting Tracker file system data miner...
Jan  4 07:51:51 guillaume-pc systemd[1494]: Started D-Bus User Message Bus.
Jan  4 07:51:52 guillaume-pc dbus-daemon[1114]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=125 pid=1527 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Jan  4 07:51:52 guillaume-pc systemd[1]: Starting RealtimeKit Scheduling Policy Service...

FrancisFDZ

Re : Partition / remplie

Bonjour,
Je trouve qu'il y a pas mal de signalements d'erreur qui concernent le réseau (NetWorkManager, wpa_supplicant, avahi_daemon ...)
freshclam dépend de clamav (clamav est-il bien indispensable ?)

---

-- On peut avoir des raisons de se plaindre et n'avoir pas raison de se plaindre --
[Victor Hugo]

geole

Re : Partition / remplie

Il me semble que le problème en cours est sur vboxdrv
pour en savoir un peu plus

journalctl -b  | tail -1000 >Trace.txt && xdg-open Trace.txt

Pour récupérer un peu de place.

sudo rm -v /var/log/syslog.*.*

Dernière modification par geole (Le 18/01/2022, à 21:48)

---

Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit,  utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir  https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Qid

Re : Partition / remplie

quasiment plus de place.

je rappelle que pour commencer dans ce genre de situation ce serait bien d'avoir le réflexe d'utiliser le logiciel graphique analyseur d'utilisation des disques présent par défaut sur ubuntu pour pouvoir déterminer seul ce qui prend de la place... il existe aussi un équivalent en terminal qui lui n'est pas installé par défaut : ncdu

Je l'ai utilisé, c'est ce que j'écris plus bas dans mon premier message.

autant pour moi... désolé pour mon intervention quasiment inutile du coups...
reste effectivement à comprendre pourquoi les log prennent autant d’embonpoint

---

"GNU/Linux c'est que du bon mais M$ Windows ce n'est pas si mal"
Référent technique Ubuntu d'un Groupe d'Utilisateur du Libre
plus d'info sur mon profil

bzh-utilisateur

Re : Partition / remplie

Trace.txt :

janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc rsyslogd[1154]: file '/var/log/syslog'[7] write error - see [url]https://www.rsyslog.com/solving-rsyslog-write-errors/[/url] for help OS error: No space left on device [v8.2001.0 try [url]https://www.rsyslog.com/e/2027[/url] ]
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:35 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Invalid password
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: The Secure Boot key you've entered is not valid. The password used must be
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: between 8 and 16 characters.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter a password for Secure Boot. It will be asked again after a reboot.
janv. 19 10:13:36 guillaume-pc vboxdrv.sh[6294]: Enter the same password again to verify you have typed it correctly.

guillaume@guillaume-pc:~$ sudo rm -v /var/log/syslog.*.*
[sudo] Mot de passe de guillaume : 
'/var/log/syslog.1.gz' supprimé
'/var/log/syslog.1.gz-2022011910.backup' supprimé
'/var/log/syslog.2.gz' supprimé
'/var/log/syslog.3.gz' supprimé
'/var/log/syslog.4.gz' supprimé
'/var/log/syslog.5.gz' supprimé
'/var/log/syslog.6.gz' supprimé
'/var/log/syslog.7.gz' supprimé
guillaume@guillaume-pc:~$ 

Dernière modification par bzh-utilisateur (Le 19/01/2022, à 13:30)

xubu1957

Re : Partition / remplie

Bonjour,

Comme demandé dans le premier message du tutoriel Retour utilisable de commande

Pour ajouter toi-même les balises code à ton précédent message #17 :           Merci             

• Cliquer sur  le lien « Modifier » en bas à droite du message

• Sélectionner le texte

• Cliquer sur le <> de l'éditeur de message

_ _ _

Voir règles du forum > balises BB code

Balise CODE :

C'est la balise à utiliser pour donner de longs messages d'erreurs, des contenus de fichiers de configuration, des commandes à taper, etc … Elle permet des messages plus "compacts", et est moins ambiguë que d'autres polices sur certains caractères.

Dernière modification par xubu1957 (Le 19/01/2022, à 13:40)

---

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

bzh-utilisateur

Re : Partition / remplie

Je sais, mais comme c'est un fichier .txt et non des lignes de commande je l'avais pas fait, excusez-moi.

Qid

Re : Partition / remplie

Il me semble que le problème en cours est sur vboxdrv

Il aurait un souci avec le secure boot !? Cette fonction incomprise ferait encore parler d'elle !? Mais c'est vrais ça : ça sert à quoi de garder ça actif !?

---

"GNU/Linux c'est que du bon mais M$ Windows ce n'est pas si mal"
Référent technique Ubuntu d'un Groupe d'Utilisateur du Libre
plus d'info sur mon profil

bzh-utilisateur

Re : Partition / remplie

Conséquence (inattendue) de mon problème, je ne peut plus télécharger des documents (issus de mails ou autres) car mon disque est plein.

Je trouve cette erreur incompréhensible et j'ai besoin de vos lumière pour m'éclairer.
On est bien d'accord que mes partitions / et /home sont séparées. Donc, actuellement /home n'est pas entièrement utilisé alors que / si.

guillaume@guillaume-pc:~$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev               6,8G       0  6,8G   0% /dev
tmpfs              1,4G    1,9M  1,4G   1% /run
/dev/sdc1           46G     44G     0 100% /
tmpfs              6,8G       0  6,8G   0% /dev/shm
tmpfs              5,0M    4,0K  5,0M   1% /run/lock
tmpfs              6,8G       0  6,8G   0% /sys/fs/cgroup
/dev/loop0         148M    148M     0 100% /snap/chromium/1854
/dev/loop1         148M    148M     0 100% /snap/chromium/1864
/dev/loop2          56M     56M     0 100% /snap/core18/2253
/dev/loop3         128K    128K     0 100% /snap/bare/5
/dev/loop6          66M     66M     0 100% /snap/gtk-common-themes/1519
/dev/loop5         219M    219M     0 100% /snap/gnome-3-34-1804/72
/dev/loop7         248M    248M     0 100% /snap/gnome-3-38-2004/87
/dev/loop4          62M     62M     0 100% /snap/core20/1242
/dev/loop8          66M     66M     0 100% /snap/gtk-common-themes/1515
/dev/loop9         165M    165M     0 100% /snap/gnome-3-28-1804/161
/dev/loop10         51M     51M     0 100% /snap/snap-store/547
/dev/loop11         56M     56M     0 100% /snap/core18/2284
/dev/loop12         44M     44M     0 100% /snap/snapd/14295
/dev/loop13        219M    219M     0 100% /snap/gnome-3-34-1804/77
/dev/loop14         62M     62M     0 100% /snap/core20/1270
/dev/loop15         55M     55M     0 100% /snap/snap-store/558
/dev/loop16         43M     43M     0 100% /snap/snapd/14066
/dev/sda1          256M     73M  184M  29% /boot/efi
/dev/sdc3           57G    3,0G   51G   6% /home
tmpfs              1,4G     40K  1,4G   1% /run/user/1000
guillaume@guillaume-pc:~$

On voit bien que sur /dev/sdc1, / est utilisé à 100% alors que sur /dev/sdc3, /home n'est utilisé qu'à 6%.

Or, lors d'un téléchargement, c'est /home, dans le répertoire /home/user/Téléchargements qui est utilisé. Alors, pourquoi je ne peut pas télécharger de documents ?

Dernière modification par bzh-utilisateur (Le 19/01/2022, à 13:39)

Qid

Re : Partition / remplie

Or, lors d'un téléchargement, c'est /home, dans le répertoire /home/user/Téléchargements qui est utilisé. Alors, pourquoi je ne peut pas télécharger de documents ?

Hum... L'utilisation de /tmp (fichiers temporaires) ne pourrait pas être responsable ?

---

"GNU/Linux c'est que du bon mais M$ Windows ce n'est pas si mal"
Référent technique Ubuntu d'un Groupe d'Utilisateur du Libre
plus d'info sur mon profil

MicP

Re : Partition / remplie

Bonjour

… Or, lors d'un téléchargement, c'est /home, dans le répertoire /home/user/Téléchargements qui est utilisé. …

Oui, quand le téléchargement est terminé, le fichier est bien inscrit dans le système de fichiers utilisé par ton répertoire personnel,
mais en cours de téléchargement, le programme de téléchargement a besoin d'écrire dans le répertoire /var/log et peut-être aussi dans d'autres répertoires
et ces répertoires sont dans le système de fichiers racine qui est déjà saturé.

=======
À mon humble avis, je pense que tu devrais t'arranger pour désinstaller virtualbox
et faire ensuite un test pour voir si le fichier /var/log/syslog continue à grossir comme avant

Mais peut-être que rien que pour désinstaller virtualbox,
il te faudra commencer par supprimer les fichiers /var/log/syslog* qui prennent trop de place.

=======
Si ça se trouve, c'est simplement une mise à jour qui manquait,
mais c'est le même problème : pour pouvoir faire cette mise à jour,
il faudra qu'il y ait un peu d'espace disponible dans le système de fichiers racine de ton système ubuntu.

Dernière modification par MicP (Le 19/01/2022, à 14:06)

cqfd93

Re : Partition / remplie

Bonjour,

Attention, l'énorme fichier /var/log/syslog.1 n'a pas été supprimé, mais quand il le sera, /var/log/syslog pourra enfler encore plus à son aise…

---

− cqfd93 −

MicP

Re : Partition / remplie

Tu pourrais limiter à 100MB la taille maximum du fichier /var/log/syslog et de ses archives
en ajoutant dans le fichier /etc/logrotate.d/rsyslog
(le temps de trouver ce qui cloche)
la directive suivante :

size 100M 

Actuellement, sur mon système Ubuntu 20.04.3 LTS
le fichier /etc/logrotate.d/rsyslog contient :

/var/log/syslog
{
	rotate 7
	daily
	missingok
	notifempty
	delaycompress
	compress
	postrotate
		/usr/lib/rsyslog/rsyslog-rotate
	endscript
}

/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
	rotate 4
	weekly
	missingok
	notifempty
	compress
	delaycompress
	sharedscripts
	postrotate
		/usr/lib/rsyslog/rsyslog-rotate
	endscript
}

et en y ajoutant cette directive,
le contenu du fichier /etc/logrotate.d/rsyslog
sera :

/var/log/syslog
{
	rotate 7
        size 100M 
	daily
	missingok
	notifempty
	delaycompress
	compress
	postrotate
		/usr/lib/rsyslog/rsyslog-rotate
	endscript
}

/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
	rotate 4
	weekly
	missingok
	notifempty
	compress
	delaycompress
	sharedscripts
	postrotate
		/usr/lib/rsyslog/rsyslog-rotate
	endscript
}

Juste après avoir ajouté cette directive,
il faudra supprimer (pour une seule fois) les fichiers /var/log/syslog*

sudo  rm  -rf  /var/log/syslog*

=======
Et quand on aura trouvé d'où vient le problème,
on pourra enlever cette directive du fichier /etc/logrotate.d/rsyslog

Dernière modification par MicP (Le 19/01/2022, à 14:27)