Outils pour utilisateurs

Outils du site


blog

Pb NFS

Err Stale File Handles

Source : https://www.baeldung.com/linux/stale-file-handles

$ stat filename
File: filename
Size: 583 Blocks: 8 IO Block: 4096 regular file
Device: 810h/2064d Inode: 666 Links: 1
[...]

$ ls -l /proc/1296/fd
total 0
lrwx------ 1 user user 64 Jul 1 10:49 0 -> /dev/pts/1
lrwx------ 1 user user 64 Jul 1 10:49 1 -> /dev/pts/1
lrwx------ 1 user user 64 Jul 1 10:49 2 -> /dev/pts/1
lrwx------ 1 user user 64 Jul 1 10:50 3 -> /home/user/filename

$ stat -L /proc/1296/fd/3
File: /proc/1296/fd/3
Size: 583 Blocks: 8 IO Block: 4096 regular file
Device: 810h/2064d Inode: 666 Links: 1
2025/03/24 15:06

Pb namespace nsenter - err reassociate to namespace ns net failed invalid argument

Voir :

nsenter --net=/run/user/1003457/netns/netns-6ab369e2-108b-8f4b-40a4-4bef511c1b9a bash

Erreur

nsenter: reassociate to namespace 'ns/net' failed: Invalid argument

Solution

$ docker inspect -f '{{.NetworkSettings.SandboxKey}}' 6b831cc17b30
/run/user/1003457/netns/netns-6ab369e2-108b-8f4b-40a4-4bef511c1b9a

$ docker inspect -f '{{.State.ConmonPid}}' 6b831cc17b30
51815

Avec le compte root

sudo nsenter -m -t 51815 nsenter --net=/run/user/1003457/netns/netns-6ab369e2-108b-8f4b-40a4-4bef511c1b9a bash

Ou avec Podman en mode rootless

podman unshare nsenter --net=/run/user/1003457/netns/netns-6ab369e2-108b-8f4b-40a4-4bef511c1b9a

Autres

$ podman inspect a9b6b3939b19 | grep '/run/user/.*ns'
               "SandboxKey": "/run/user/1000/netns/netns-b6cd07ab-1512-c5af-419a-95b91701cfe0"

$ podman inspect a9b6b3939b19 --format "{{ .State.Pid }}"
24864

$ podman unshare nsenter --net=/run/user/1000/netns/netns-b6cd07ab-1512-c5af-419a-95b91701cfe0
2025/03/24 15:06

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

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

http://askubuntu.com/questions/605369/mce-hardware-error-machine-check-events-logged-appears-in-syslog-what-sho

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.

2025/03/24 15:06

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
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