La commande top lancée sur le serveur vous affiche une charge de 1 et vous ne voyez pourtant aucun processus prendre toutes les ressources ? regardez un peu dans les logs (tail -f /var/log/syslog) et si vous avez quelque-chose de ce genre c'est que vous êtes victime d'un bug du bus USB !
Oct 12 20:17:20 servecole kernel: [ 5558.506940] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:21 servecole kernel: [ 5558.714979] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:22 servecole kernel: [ 5560.634481] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:23 servecole kernel: [ 5560.842523] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:25 servecole kernel: [ 5562.762022] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:25 servecole kernel: [ 5562.969973] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:27 servecole kernel: [ 5564.889562] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:27 servecole kernel: [ 5565.097602] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:29 servecole kernel: [ 5567.017099] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:29 servecole kernel: [ 5567.225050] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:31 servecole kernel: [ 5569.144640] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:31 servecole kernel: [ 5569.352584] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:33 servecole kernel: [ 5571.272177] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:33 servecole kernel: [ 5571.480123] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:35 servecole kernel: [ 5573.399714] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:35 servecole kernel: [ 5573.607661] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:37 servecole kernel: [ 5575.527251] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:38 servecole kernel: [ 5575.735196] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:39 servecole kernel: [ 5577.654784] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:40 servecole kernel: [ 5577.862711] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:42 servecole kernel: [ 5579.782322] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:42 servecole kernel: [ 5579.990366] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:44 servecole kernel: [ 5581.909855] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:44 servecole kernel: [ 5582.117894] hub 3-0:1.0: over-current condition on port 2 Oct 12 20:17:46 servecole kernel: [ 5584.037403] hub 3-0:1.0: connect-debounce failed, port 2 disabled Oct 12 20:17:46 servecole kernel: [ 5584.245426] hub 3-0:1.0: over-current condition on port 1 Oct 12 20:17:48 servecole kernel: [ 5586.164922] hub 3-0:1.0: connect-debounce failed, port 1 disabled Oct 12 20:17:48 servecole kernel: [ 5586.372960] hub 3-0:1.0: over-current condition on port 2
Heureusement pour vous les Horizon System Tools sont là !
horizon-usb-reset.sh
Patientez un peu, la commande en question stoppe tous les périphériques USB, supprime les drivers (modules) usb, les réinstalle … et normalement vous ne devriez plus avoir d'erreurs dans les logs … et la charge système du serveur va retourner dans les 0.xx … et le ventilateur arrêter de tourner comme un fous !