blog
Table des matières
3 billet(s) pour janvier 2026
| Notes rsh rcp | 2026/01/21 18:08 | Jean-Baptiste |
| Git - Duplication d'un dépôt | 2026/01/19 10:22 | Jean-Baptiste |
| Exemple simple de conf Nagios | 2026/01/14 10:07 | Jean-Baptiste |
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 !?
Pb DokuWiki plugin sqlite HY000 1 no such table opts
Liens :
HY000 1 no such table: opts:
sqlite3 dokuwiki/data/meta/plop.sqlite3
CREATE TABLE opts (opt,val); CREATE UNIQUE INDEX idx_opt ON opts(opt); INSERT INTO opts (val,opt) VALUES (1,'dbversion'); SELECT * FROM opts;
Pb Docker RHEL CentOS 5 et 6
Voir :
$ docker run --rm -ti centos:centos5 /bin/bash [139] $ $ docker run --rm -ti centos:centos6 /bin/bash [139] $
Impossible de lancer la plupart des commandes. Code de retour d'erreur : 139
Solution
Sur le hôte passer au Kernel Linux l'argument suivant :
vsyscall=emulate
La version de la glibc est trop ancienne et utilise dans anciens appels système !?
Exécutez la commande suivante pour vérifier que votre système a désactivé vsyscall:
cat /proc/self/maps | egrep 'vdso|vsyscall'
La sortie sera semblable à ce qui suit:
7fffccfcc000-7fffccfce000 r-xp 00000000 00:00 0 [vdso]
ou à celui-ci:
7fffe03fe000-7fffe0400000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
vsyscall= [X86-64,EARLY] Controls the behavior of vsyscalls (i.e. calls to fixed addresses of 0xffffffffff600x00 from legacy code). Most statically-linked binaries and older versions of glibc use these calls. Because these functions are at fixed addresses, they make nice targets for exploits that can control RIP. emulate Vsyscalls turn into traps and are emulated reasonably safely. The vsyscall page is readable. xonly [default] Vsyscalls turn into traps and are emulated reasonably safely. The vsyscall page is not readable. none Vsyscalls don't work at all. This makes them quite hard to use for exploits but might break your system.
blog.txt · Dernière modification : de 127.0.0.1