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 memoire cpu hardware mcelog
Le paquet mcelog n'est plus pris en charge dans les noyaux 4.12 et suivants. rasdaemon peut être utilisé comme remplacement
rasdaemon
utility to receive RAS error tracings rasdaemon is a RAS (Reliability, Availability and Serviceability) logging tool. It currently records memory errors, using the EDAC tracing events. EDAC are drivers in the Linux kernel that handle detection of ECC errors from memory controllers for most chipsets on x86 and ARM architectures. This userspace component consists of an init script which makes sure EDAC drivers and DIMM labels are loaded at system startup, as well as a utility for reporting current error counts from the EDAC sysfs files
I enable memory error reporting
http://www.mcelog.org/faq.html
chkconfig mcelog on rcmcelog start
/etc/cron.hourly/mcelog.cron
#!/bin/bash # is mcelog supported? /usr/sbin/mcelog --supported >& /dev/null if [ $? -eq 1 ]; then exit 1; fi /usr/sbin/mcelog --ignorenodev --filter >> /var/log/mcelog
sudo apt-get install mcelog
The events will be logged to /var/log/mcelog. You can also run:
sudo mcelog --client
II
# mcelog mcelog: AMD Processor family 18: Please use the edac_mce_amd module instead. : Success CPU is unsupported
lsmod |grep edac_mce_amd modprobe edac_mce_amd echo edac_mce_amd >> /etc/modules
III
http://www.advancedclustering.com/act-kb/what-are-machine-check-exceptions-or-mce/
Paste or type the error message into a file, and then run it through the mcelog for example:
/usr/sbin/mcelog --k8 --ascii < myerror
Use the –k8 option if you are using an AMD Opteron or Athlon 64 processor, or substitute it for –p4 for a Pentium 4 or Xeon. Here is the output from the previous MCE error:
HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 1 4 northbridge TSC b0ce27165dd3 Northbridge Chipkill ECC error Chipkill ECC syndrome = 3700 bit32 = err cpu0 bit45 = uncorrected ecc error bit57 = processor context corrupt bit61 = error uncorrected bit62 = error overflow (multiple errors) bus error 'local node origin, request didn't time out generic read mem transaction memory access, level generic' STATUS f600200137080813 MCGSTATUS 4
This indicates that an uncorrected ECC error occurred. This indicates that one of your memory modules has failed. For further analysis please submit a support ticket with the complete MCE error message and the output of mcelog.
Pb make Makefile missing separator
Makefile:13: *** missing separator (did you mean TAB instead of 8 spaces?). Stop.
Solution
sed -i -e 's/^[ ]\+/\t/' Makefile
Cloud AWS - CloudFormation
Voir :
Voir aussi :
wget https://s3-eu-west-1.amazonaws.com/cloudformation-templates-eu-west-1/EC2InstanceWithSecurityGroupSample.template mv EC2InstanceWithSecurityGroupSample.template single-instance.json python -c 'import sys, yaml, json; yaml.safe_dump(json.load(sys.stdin), sys.stdout, default_flow_style=False)' < single-instance.json > single-instance.yml aws cloudformation create-stack --template-body file://single-instance.yml --stack-name single-instance --parameters ParameterKey=KeyName,ParameterValue=admin@be-poc-build01 ParameterKey=InstanceType,ParameterValue=t2.micro ParameterKey=VPC,ParameterValue=vpc-0e2a03558daf2e463 ParameterKey=Subnets,ParameterValue=subnet-0d63fcd2f893bbb9b aws cloudformation delete-stack --stack-name single-instance
Pb LVM
Erreur Device /dev/sda excluded by a filter.
Device /dev/sda excluded by a filter.
Solutions
Solutions
dd if=/dev/zero of=/dev/sda count=1 bs=512
Ou (à tester)
sgdisk --zap-all -- /dev/sda
Erreur /dev/sdb: open failed: No medium found
# vgs /dev/sdb: open failed: No medium found VG #PV #LV #SN Attr VSize VFree vg_data 1 1 0 wz--n- <931.51g 930.55g vgos 1 4 0 wz--n- <237.52g 79.82g # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part └─vg_data-data 254:5 0 976M 0 lvm nvme0n1 259:0 0 238.5G 0 disk ├─nvme0n1p1 259:1 0 488M 0 part /boot ├─nvme0n1p2 259:2 0 488M 0 part /boot/efi └─nvme0n1p3 259:3 0 237.5G 0 part ├─vgos-root 254:0 0 46.6G 0 lvm / ├─vgos-swap 254:1 0 15.3G 0 lvm [SWAP] ├─vgos-var 254:2 0 55.9G 0 lvm /var └─vgos-home 254:3 0 40G 0 lvm /home
Dans notre cas nous avons un /dev/sdb fantome
# fdisk /dev/sdb Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sdb: No medium found
Solution
Solution temporaire
# mv /dev/sdb . # vgs VG #PV #LV #SN Attr VSize VFree vg_data 1 1 0 wz--n- <931.51g 930.55g vgos 1 4 0 wz--n- <237.52g 79.82g
Erreur Locking type -1 initialisation failed
Voir :
Solution
- Vérifier si /var n'est pas monté en lecture seul (voir
locking_dirdanslvm.conf) - Utiliser l'option
--ignorelockingfailure
Exemple 1
vgchange --ignorelockingfailure -P -a y
Exemple 2
pvs --config 'global { locking_dir = "/tmp" }
Err Device mismatch detected
Source : https://documentation.commvault.com/commvault/v11_sp16/article?p=31713.htm
Cause
If the virtual machine where a File Recovery Enabler for Linux is installed is based on the same VM template or image as the guest virtual machines or instances that the FREL is browsing, then live browse of files and folders on the guest VMs might fail as a result of UUID conflicts with physical volumes (PVs) on the FREL.
Resolution
To resolve this issue, change the UUIDs of the PVs on the FREL:
List all the physical volumes:
pvs -o --noheadings
Change the UUID for each PV listed in step 1.
pvchange -f --uuid pv_name --config "global {activation=0}"
List all the volume groups:
vgs -o vg_name,vg_uuid,pv_name --noheadings
Run the following commands to change the UUIDs and rename each of the volume groups listed in step 3 and activate the changed configuration:
vgchange --uuid vg_name --config "global {activation=0}"
vgrename old_vg_name new_vg_name
vgchange -ay new_vg_name
Autres RO FS
touch /plop
touch: ne peut faire un touch sur `/plop': Système de fichiers accessible en lecture seulement
blockdev --setrw /dev/sda mount -o remount,rw /
mount: périphérique de type bloc/dev/VolGroup00/LogVol00 est protégé en écriture, on le monte en lecture seulement
pvdisplay
Locking type -1 initialisation failed.
Exemple de commande en lien, à tester
vgchange --ignorelockingfailure -P -a y vgchange -a y VolGroup-1 blockdev --rereadpt /dev/sda
A voir aussi
lvm.conf
/etc/lvm/lvm.conf locking_type = 1 locking_dir = "/var/lock/lvm"
lvchange -p rw lvm vgchange -ayl --ignorelockingfailure lvm vgmknodes --ignorelockingfailure if touch -c / >& /dev/null
Pb /dev/mapper missing LV
Solution
vgscan --mknodes
Pb LibVirt Failed to start network default Unable to create bridge virbr0 Le fichier existe
Pb
virsh # net-start default error: Failed to start network default error: Unable to create bridge virbr0: Le fichier existe
Solution
ifconfig virbr0 down
brctl delbr virbr0
virsh net-start default