Outils pour utilisateurs

Outils du site


blog

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;
2025/03/24 15:06

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

Source : https://unix.stackexchange.com/questions/478387/running-a-centos-docker-image-on-arch-linux-exits-with-code-139ù

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.
2025/03/24 15:06

Pb Docker Podman

Err cannot set user namespace

$ podman ps
cannot set user namespace
Solution
mv /tmp/podman-run-1000 /tmp/podman-run-1000-bak
2025/03/24 15:06

Pb Docker - device is busy - error response from daemon driver devicemapper failed to remove root filesystem

Source : https://github.com/moby/moby/issues/27381

Pb

# docker rm -f c67056cc52ec
Error response from daemon: driver "devicemapper" failed to remove root filesystem for c67056cc52ec0053f08e3bb847ac9c5ec0617bfe99056e0a3371410c80ac9921: failed to remove device 986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e
58e: Device is Busy

# rm -rf  /var/lib/docker/devicemapper/*/*e58e*                                                                                                                                                    
rm: impossible de supprimer « /var/lib/docker/devicemapper/mnt/986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e »: Périphérique ou ressource occupé

Solution

# find /proc/*/mounts | xargs grep 986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e
grep: /proc/10975/mounts: Aucun fichier ou dossier de ce type
/proc/14426/mounts:/dev/mapper/docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e /var/lib/docker/devicemapper/mnt/986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e ext4 rw,relatime,stripe=16,data=ordered 0 0
# ps -p 14426
  PID TTY          TIME CMD
14426 ?        00:00:00 cupsd
# kill 14426
# docker rm c67056cc52ec

Notes

LANG=C dmsetup remove docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e                                                                                       
device-mapper: remove ioctl on docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e failed: Device or resource busy

dmsetup info -c docker-254:2-183267-986d057a397700ab66df675365e53c2e8e6b129cc743bbc3bb6e9cc92510e58e

La technique suivante n'a pas fonctionné https://askubuntu.com/questions/429612/device-mapper-remove-ioctl-on-luks-xxxx-failed-device-or-resource-busy

$ sudo dmsetup ls
luks-xxxxx (252:1)
$ sudo lsof | grep 252,1
$ kill -9 1523
2025/03/24 15:06

Pb DNS resolution - systemd-resolved - timeout short name

$ host www.acme.fr
www.acme.fr has address 192.168.1.100
$ time host plop
;; connection timed out; no servers could be reached

real    0m10.033s
user    0m0.009s
sys     0m0.005s
$ systemd-resolve www.acme.fr
www.acme.fr: 192.168.1.100
                                          (www.acme.fr)

-- Information acquired via protocol DNS in 1.7ms.
-- Data is authenticated: no
$ systemd-resolve plop
plop: resolve call failed: All attempts to contact name servers or networks failed

Solution

Désactiver LLMNR

/etc/systemd/resolved.conf.d/dns_servers.conf

[Resolve]
LLMNR=no

Autres

journalctl -u systemd-resolved.service -f
2025/03/24 15:06
blog.txt · Dernière modification : de 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki