Bonjour
Je viens vers vous car j’en perd un peu mon latin
j’ai un serveur (squeeze) surchargé, mais je n’arrive pas à trouver l’origine du probleme
voila le résultat d’un top
top - 10:20:09 up 37 days, 20:14, 1 user, load average: 35.10, 35.29, 35.49
Tasks: 389 total, 1 running, 388 sleeping, 0 stopped, 0 zombie
Cpu0 : 0.2%us, 0.0%sy, 0.0%ni, 49.4%id, 50.4%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu1 : 0.2%us, 0.2%sy, 0.0%ni, 0.0%id, 99.5%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 0.6%sy, 0.0%ni, 19.3%id, 80.2%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 : 0.5%us, 1.0%sy, 0.0%ni, 98.5%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8178584k total, 6716256k used, 1462328k free, 1351280k buffers
Swap: 12292384k total, 130168k used, 12162216k free, 2146932k cached
Comment avoir un load average à 35 avec des cpu qui ne font rien!!
et j’ai fait une recherche via nload et je n’ai pas de traffic sup a 1Mbits/s en ce moment
enfin derniere info:
dmesg|tail
[2573341.452326] ct0 statd: server rpc.statd not responding, timed out
[2573341.452345] lockd: cannot monitor hastur
[2573401.452533] ct0 statd: server rpc.statd not responding, timed out
[2573401.452552] lockd: cannot monitor hastur
[2573461.452526] ct0 statd: server rpc.statd not responding, timed out
[2573461.452544] lockd: cannot monitor hastur
[2573521.452525] ct0 statd: server rpc.statd not responding, timed out
[2573521.452545] lockd: cannot monitor hastur
[2664325.434926] Registering the dns_resolver key type
[3234280.118791] scanning ...
c’est quoi ça?
ct0 statd: server rpc.statd not responding, timed out
lockd: cannot monitor hastur
merci pour votre coup de main.