blog
Table des matières
- 2026:
- 2025:
13 billet(s) pour novembre 2026
| Réseaux - protocole QUIC mieux que TCP | 2026/11/17 21:26 | Jean-Baptiste |
| Notes conversion JSON YAML | 2026/11/13 11:16 | Jean-Baptiste |
| Git commit perdu | 2026/11/12 18:16 | Jean-Baptiste |
| Notes mojo lang | 2026/11/11 20:34 | Jean-Baptiste |
| Notes rust lang compilation | 2026/11/11 18:35 | Jean-Baptiste |
| Mémoire VSIZE VMSIZE SEGV lang C | 2026/11/11 15:59 | Jean-Baptiste |
| Ansible-navigator utilisation de ansible-vault | 2026/11/06 11:33 | Jean-Baptiste |
| Err Ansible - Module result deserialization failed No start of json char found | 2026/11/06 09:09 | Jean-Baptiste |
| Script Python conversion JSON vers CSV | 2026/11/06 08:14 | Jean-Baptiste |
| Filter Incoming IPv4 Packets Containing IP Options - cve-2026-98432 mitigation - Kernel TCP Use-After-Free | 2026/11/04 21:04 | Jean-Baptiste |
| Notes ZFS | 2026/11/03 18:04 | Jean-Baptiste |
| Diff image container | 2026/11/03 16:30 | Jean-Baptiste |
| Notes processus multi-thread | 2026/11/03 10:59 | Jean-Baptiste |
Pb Err Failed to connect to bus: No such file or directory
$ systemctl --user enable --now redshift Failed to connect to bus: Aucun fichier ou dossier de ce type
Solution
export XDG_RUNTIME_DIR=/run/user/`id -u`
Est-ce que systemd est bien démarré en userland
$ ps -u $USER -f --no-headers | head -1 k8s 1333 1 0 21:56 ? 00:00:00 /usr/lib/systemd/systemd --user
Est-ce que le lingering est activé ?
Si vous avez terminez le process /usr/lib/systemd/systemd vous pouvez sous le compte root faire :
service systemd-logind status
Cela va relancer le process /usr/lib/systemd/systemd --user dans le userland des comptes qui ont le lingering activé
Autres
loginctl enable-linger $username sudo service systemd-logind status sudo apt install dbus-user-session sudo apt install --reinstall libpam-systemd sudo systemctl start dbus
Pb Err dmesg EXT4-fs error count initial error
Source : https://lkml.org/lkml/2010/9/26/105
# #dmesg -l warn | tail # dmesg | tail [8141220.179232] : inode 6946817: block 27787296 [8141220.179237] EXT4-fs (dm-4): error count: 48 [8141220.179243] EXT4-fs (dm-4): initial error at 1432118116: __ext4_journal_start_sb:62 [8141220.179248] EXT4-fs (dm-4): last error at 1453127164: ext4_put_super:789 [8141220.179263] EXT4-fs (dm-5): error count: 41 [8141220.179267] EXT4-fs (dm-6): initial error at 1432127211: ext4_mb_generate_buddy:755 [8141220.179270] EXT4-fs (dm-5): initial error at 1432648670: __ext4_journal_start_sb:62 [8141220.179274] EXT4-fs (dm-5): last error at 1453127158: ext4_put_super:789 [8141220.179284] EXT4-fs (dm-6): last error at 1473645508: ext4_mb_generate_buddy:755
$ date --date=@1473645508 Mon Sep 12 03:58:28 CEST 2016
Ou plus simple, pour avoir les dates et heures
dmesg -T
Généralement peut être ignoré.
Pb encodage charset Apache PHP
<VirtualHost *:80> ServerName www.acme.fr ServerAdmin webmaster ServerSignature Off DirectoryIndex index.htm index.html index.php AddDefaultCharset ISO-8859-15 php_value default_charset ISO-8859-15 </VirtualHost>
Il est plutôt recommandé d'utiliser UTF8
Pb effacement dev loop0 - cannot delete device dev loop0
Source : https://stackoverflow.com/questions/5881134/cannot-delete-device-dev-loop0
dmsetup remove_all dmsetup remove <device> dmsetup info
Notes dmsetup
dmsetup table
Pb edac mc0
Voir :
Voir aussi :
- edac-ctl
# dmesg [2687274.808024] EDAC MC0: 1 CE x38 CE on mc#0csrow#6channel#0 or mc#0csrow#6channel#1 (csrow:6 page:0x0 offset:0x0 grain:1073741824 syndrome:0x92) [2687275.808024] EDAC MC0: 1 CE x38 CE on mc#0csrow#6channel#0 or mc#0csrow#6channel#1 (csrow:6 page:0x0 offset:0x0 grain:1073741824 syndrome:0x92) [2687276.808023] EDAC MC0: 1 CE x38 CE on mc#0csrow#6channel#0 or mc#0csrow#6channel#1 (csrow:6 page:0x0 offset:0x0 grain:1073741824 syndrome:0x92)
# cat /sys/module/edac_core/parameters/edac_mc_log_ce 1
# cat /sys/devices/system/edac/mc/mc0/ce_count 441674
Solution ?
Mise-à-jour système et redémarrage !?
blog.txt · Dernière modification : de 127.0.0.1
