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 boot Debian Stretch carte graphique nvidia erreur CPU stuck
Erreur :
BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:2813]
Voir :
Test avec parametres noyau suivants :
noapic nolapic acpi=off
Ca boot grâce à acpi=off
Le pb vient du driver nouveau /etc/modprobe.d/nvidia-disable-nouveau.conf
blacklist nouveau
Cloud - packer.io
Voir aussi :
Config
Prereq
~/.aws/config
[default] region = us-east-2 output = table
~/.aws/credentials
[default] aws_access_key_id = AKIAR5WS3MDOSPIUHRU7 aws_secret_access_key =
Exécution
packer/example.json
{ "variables": { "aws_access_key": "", "aws_secret_key": "" }, "provisioners": [{ "type": "ansible", "playbook_file": "../ansible/play-test.yml" }], "builders": [{ "type": "amazon-ebs", "access_key": "{{user `aws_access_key`}}", "secret_key": "{{user `aws_secret_key`}}", "region": "us-east-2", "source_ami_filter": { "filters": { "virtualization-type": "hvm", "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], "most_recent": true }, "instance_type": "t2.micro", "ssh_username": "ubuntu", "ami_name": "packer-example {{timestamp}}" }] }
ansible/play-test.yml
--- - name: test1 hosts: all become: true vars: ansible_python_interpreter: /usr/bin/python3 tasks: - name: plop shell: echo plop > /plop
packer validate example.json packer build example.json
Debug
packer build --debug example.json
Pour pouvoir se connecter en SSH sur l'instance.
"ssh_keypair_name": "nom_de_la_clef_presente_sur_aws", "ssh_private_key_file": "/home/admin/.ssh/id_rsa",
| ssh_keypair_name | Nom de la pair de clefs présente sur AWS. Utilisé par AWS pour créer l'instance |
| ssh_private_key_file | Chemin de la clef privée pour que Packer puisse se connecter sur l'instance |
Normalement seul ssh_username est nécessaire à la création de l'AMI.
Pour se connecter en SSH sur une instance déjà crée
$ ps -ef |grep ssh ssh -o ControlMaster=auto -o ControlPersist=30m -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Port=39087 -o IdentityFile="/tmp/ansible-key896233465" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User="admin" -o ConnectTimeout=10 -o ControlPath=/home/admin/.ansible/cp/d7af4b579b 127.0.0.1 /bin/sh
ssh admin@localhost -i /tmp/ansible-key896233465 -p 39087 /bin/bash ansible-playbook --extra-vars packer_build_name=amazon-ebs -e packer_builder_type=amazon-ebs -i /tmp/packer-provisioner-ansible966542596 /home/admin/workspace/Deploy_AMI_SCM_v2/905239-packebuild/ansible/playbook.yml -e ansible_ssh_private_key_file=/tmp/ansible-key896233465
Pb Asus K53TA X11 est très long a démarrer
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="radeon.runpm=0"
sudo update-grub
Voir https://bbs.archlinux.org/viewtopic.php?id=177254
/etc/modprobe.d/boot_radeon.conf
options radeon dpm=1 options radeon audio=1 options radeon runpm=0
sudo update-initramfs -k all -u
cat /sys/kernel/debug/vgaswitcheroo/switch echo OFF > /sys/kernel/debug/vgaswitcheroo/switch echo DIS > /sys/kernel/debug/vgaswitcheroo/switch
Pb apt-get update
Pb appstreamcli
# apt-get update Fetched 61.8 MB in 12s (5,054 kB/s) The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information. Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /d ev/null; fi' E: Sub-process returned an error code
Solution
appstreamcli refresh-cache --force
Pb apt-get hang out
# strace -ff apt-get update
...
[pid 29158] select(6, [5], [], NULL, {tv_sec=0, tv_usec=500000}) = 0 (Timeout)
[pid 29158] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
[pid 29158] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
0% [Working]) = 131, "\r0% [Working]", 13
[pid 29158] select(6, [5], [], NULL, {tv_sec=0, tv_usec=500000}) = 0 (Timeout)
[pid 29158] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
[pid 29158] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
0% [Working]) = 131, "\r0% [Working]", 13
[pid 29158] select(6, [5], [], NULL, {tv_sec=0, tv_usec=500000}) = 0 (Timeout)
[pid 29158] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
[pid 29158] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
0% [Working]) = 131, "\r0% [Working]", 13
[pid 29158] select(6, [5], [], NULL, {tv_sec=0, tv_usec=500000}) = 0 (Timeout)
[pid 29158] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
[pid 29158] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
0% [Working]) = 131, "\r0% [Working]", 13
Solution
Corriger /etc/resolv.conf
#domain acme.local search acme.local options rotate timeout:1 retries:1 nameserver 192.168.1.1 nameserver 8.8.8.8
Pb apt update Debian9 - Err dep-11 404 Not Found
Contexte : Pb lors de la mise à jour depuis une ancienne Debian 9 testing
Le même pb et solution sur Ubuntu : https://askubuntu.com/questions/786733/apt-get-update-command-not-working-from-xenial-local-Mirror
La solution proposée fonctionne :
rm /etc/apt/apt.conf.d/50appstream
Autre solution : Désinstaller appstream
apt-get purge $(dpkg -l | grep appstream | awk '{print $2}')
blog.txt · Dernière modification : de 127.0.0.1
