AdminSysGNULinux

Outils pour utilisateurs

Outils du site

Piste : • blog
blog

Table des matières

3 billet(s) pour janvier 2026

Notes rsh rcp2026/01/21 18:08Jean-Baptiste
Git - Duplication d'un dépôt2026/01/19 10:22Jean-Baptiste
Exemple simple de conf Nagios2026/01/14 10:07Jean-Baptiste

Pb LibVirt DNSMasq DNS port 53 (TCP/UDP)

$ sudo lsof -i UDP:53
COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dnsmasq 3461 nobody    6u  IPv4  27341      0t0  UDP poste1.local:domain 
$ ps -p 3461 -f
UID        PID  PPID  C STIME TTY          TIME CMD
nobody    3461     1  0 11:00 ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

/var/lib/libvirt/dnsmasq/default.conf 

##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
##    virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
pid-file=/var/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254
dhcp-no-override
dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
virsh -c qemu:///system net-edit default
2025/03/24 15:06
, ,

Pb LIBATA NCQ SSD TRIM

Voir :

Voir aussi :

Kernel parameter 

libata.force=noncq
libata.force=noncq,3.0Gbps
libata.noacpi
# cat /sys/block/sda/queue/scheduler
noop deadline [cfq]

Source : https://www.systutorials.com/241496/whats-wrong-with-the-messages-like-unrecovdata-10b8b-badcrc-and-failed-command-read-fpdma-queued-on-linux/ 

# ls -l /sys/class/block/ | grep ata4
lrwxrwxrwx 1 root root 0 May  5 15:04 sdd -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 May  5 15:04 sdd1 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd1

Pb

/var/log/kern.log
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594110] ata1.00: exception Emask 0x10 SAct 0x7fe00fff SErr 0x800100 action 0x6 frozen
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594154] ata1.00: irq_stat 0x08000000, interface fatal error
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594182] ata1: SError: { UnrecovData LinkSeq }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594206] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594232] ata1.00: cmd 61/08:00:60:10:ee/00:00:0b:00:00/40 tag 0 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594232]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594297] ata1.00: status: { DRDY }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594313] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594339] ata1.00: cmd 61/08:08:08:20:ee/00:00:0b:00:00/40 tag 1 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594339]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594404] ata1.00: status: { DRDY }
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594420] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594446] ata1.00: cmd 61/08:10:58:10:2a/00:00:0d:00:00/40 tag 2 ncq dma 4096 out
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594446]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.568 pc01 err kernel:[149221.594511] ata1.00: status: { DRDY }
/var/log/kern.log
2018-08-22T12:21:26.608 pc01 err kernel:[149221.638355] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.612 pc01 err kernel:[149221.639183] ata1.00: cmd 61/08:e8:80:10:ea/00:00:0b:00:00/40 tag 29 ncq dma 4096 out
2018-08-22T12:21:26.612 pc01 err kernel:[149221.639183]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.612 pc01 err kernel:[149221.640861] ata1.00: status: { DRDY }
2018-08-22T12:21:26.612 pc01 err kernel:[149221.641699] ata1.00: failed command: WRITE FPDMA QUEUED
2018-08-22T12:21:26.612 pc01 err kernel:[149221.642567] ata1.00: cmd 61/08:f0:10:11:eb/00:00:0b:00:00/40 tag 30 ncq dma 4096 out
2018-08-22T12:21:26.612 pc01 err kernel:[149221.642567]          res 40/00:5c:f0:50:87/00:00:0d:00:00/40 Emask 0x10 (ATA bus error)
2018-08-22T12:21:26.616 pc01 err kernel:[149221.644228] ata1.00: status: { DRDY }
2018-08-22T12:21:26.616 pc01 info kernel:[149221.645070] ata1: hard resetting link
2018-08-22T12:21:26.932 pc01 info kernel:[149221.959364] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2018-08-22T12:21:26.932 pc01 info kernel:[149221.960960] ata1.00: configured for UDMA/133
2018-08-22T12:21:26.932 pc01 info kernel:[149221.961024] ata1: EH complete
2025/03/24 15:06
, , ,

Pb lang qwerty boot cryptsetup

Voir

Cryptsetup me demande la passphrase au boot, mais rien ne marche.

Je jette un œil sur une image d'un clavier yankee, youpi !

Après le boot, toujours pareille,

J'aurais pu aussi tenter de booter sur un ancien noyau.

loadkeys fr ne fonctionne pas. La commande loadkeys n'est pas présente

Je test

Source : 

apt-get install console-data
dpkg-reconfigure console-data
dpkg-reconfigure keyboard-configuration
systemctl restart keyboard-setup
update-initramfs -u

/etc/initramfs-tools/initramfs.conf 

KEYMAP=y

En ce qui me concerne ça venait du paquet console-setup ou kdb que j'avais désinstallé 

apt-get install console-setup
loadkeys fr
update-initramfs -u
2025/03/24 15:06
, , ,

Pb Kubernetes - K8S - Node status Pending

Voir : https://repost.aws/fr/knowledge-center/eks-resolve-pending-fargate-pods 

# kubectl get pods --all-namespaces 
NAMESPACE     NAME                              READY   STATUS             RESTARTS         AGE
kube-system   coredns-6f6b679f8f-bjrwf          0/1     Pending            0                22h
kube-system   coredns-6f6b679f8f-rn9wf          0/1     Pending            0                22h

Ici c'est parce qu'aucun plugin réseau n'a été encore déployé (Cilium, Flannel, Calico, Weave…) 

kubectl describe pod coredns-6f6b679f8f-bjrwf 
# journalctl -f -u kubelet.service 
Sep 10 14:52:46 vmdeb01 kubelet[11657]: E0910 14:52:46.562785   11657 kubelet.go:2901] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
2025/03/24 15:06
, ,

Pb Kubernetes - K8S - Node status NotReady

Sur le Master 

# kubectl get nodes
NAME   STATUS     ROLES    AGE   VERSION
kub1   Ready      master   40d   v1.17.0
kub2   NotReady   <none>   40d   v1.17.0
kub3   Ready      <none>   40d   v1.17.0

# kubectl describe node kub2
  Type             Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message
  ----             ------    -----------------                 ------------------                ------              -------
  MemoryPressure   Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  DiskPressure     Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  PIDPressure      Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  Ready            Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.

Sur le Worker 

root@kub2:~# systemctl status kubelet.service

root@kub2:~# journalctl -f -u kubelet.service
Jan 29 18:51:17 kub2 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Jan 29 18:51:17 kub2 systemd[1]: Started kubelet: The Kubernetes Node Agent.
Jan 29 18:51:17 kub2 kubelet[15311]: F0129 18:51:17.486785   15311 server.go:198] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
Jan 29 18:51:17 kub2 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
Jan 29 18:51:17 kub2 systemd[1]: kubelet.service: Failed with result 'exit-code'

Solution

Sur le Master 

root@kub1:~# kubeadm token create --print-join-command
W0129 18:57:42.419029    4660 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0129 18:57:42.419636    4660 validation.go:28] Cannot validate kubelet config - no validator is available
kubeadm join 192.168.56.21:6443 --token 2sfx5v.yjb8tsilc19u43rm     --discovery-token-ca-cert-hash sha256:f84fd4960fc7844182510b8daea9eb6739af2075f79edd726b3facfc1285e291

Sur le Worker 

kubeadm join 192.168.56.21:6443 --token 2sfx5v.yjb8tsilc19u43rm     --discovery-token-ca-cert-hash sha256:f84fd4960fc7844182510b8daea9eb6739af2075f79edd726b3facfc1285e291
2025/03/24 15:06
,

<< Billets récents | Anciens billets >>

blog.txt · Dernière modification : de 127.0.0.1
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki