Bonjour,
Je viens de me rendre compte qu’une machine a de nombreux segfaults. Et évidemment je n’ai pas d’accès KVM/IP pour lancer un memtest… Vous auriez des outils pour gérer ce genre de cas ?
alarig@argall:~$ dmesg | grep segfault [8797847.703324] dpkg-preconfigu[12044]: segfault at 2000000008 ip 00007f8bb83ef530 sp 00007ffc308e5140 error 4 in libperl.so.5.20.2[7f8bb8331000+1b7000] [8797847.778480] dpkg[12046]: segfault at 2014ff946 ip 000000000040c02e sp 00007ffcf2019260 error 4 in dpkg[400000+42000] [8797902.719319] apt-get[12169]: segfault at 7f23b2d8ab48 ip 00007f03b4cfc1f9 sp 00007ffdd28b1b50 error 4 in libapt-pkg.so.4.12.0[7f03b4c3c000+168000] [8797916.087786] check_ftp[12206]: segfault at 7f7ba434afb8 ip 00007f79a402de33 sp 00007ffdbcdfbbb8 error 4 in libc-2.19.so[7f79a3fa8000+1a1000] [8797916.411782] check_http[12207]: segfault at 7f2a7cee5e48 ip 00007f0a7e358ce9 sp 00007ffece6adea0 error 4 in ld-2.19.so[7f0a7e34b000+20000] [8797920.268743] shinken-poller[18153]: segfault at 2000944640 ip 00000000004b641c sp 00007ffcb1232750 error 6 in python2.7[400000+31e000] [8797945.537473] shinken-poller[12228]: segfault at 7f432541d9d8 ip 000000000049ab62 sp 00007ffcb1232e60 error 4 in python2.7[400000+31e000] [8797947.132438] check_smtp[12331]: segfault at 7f866f1109c8 ip 00007f846e24cb3e sp 00007ffe2da427b0 error 4 in libpthread-2.19.so[7f846e246000+18000] [8797949.144224] shinken-poller[18137]: segfault at 7f430563a6a8 ip 000000000049f6c3 sp 00007ffcb1232ab0 error 4 in python2.7[400000+31e000] [8797965.240866] check_http[12364]: segfault at 7f89b3cda087 ip 00007f8bb47508f0 sp 00007ffe765748f8 error 4 in ld-2.19.so[7f8bb4739000+20000] [8797965.248510] check_imap[12365]: segfault at 7fdbaa16aff0 ip 00007ffba87a2495 sp 00007ffd03a09cb8 error 4 in libc-2.19.so[7ffba869b000+1a1000] [8797965.294364] shinken-poller[12342]: segfault at 7f612541d060 ip 00000000004e43ef sp 00007ffcb1232940 error 4 in python2.7[400000+31e000] [9423564.685198] shinken-poller[28853]: segfault at 200093beb0 ip 00000000004a0c02 sp 00007ffcb1231b90 error 6 in python2.7[400000+31e000] [9423564.686052] shinken-poller[12372]: segfault at 200093beb0 ip 00000000004ed8c4 sp 00007ffcb1232f20 error 6 in python2.7[400000+31e000] [9423565.975707] shinken-poller[18037]: segfault at 7f612541d060 ip 00000000004e43ef sp 00007f631e536900 error 4 in python2.7[400000+31e000] [9423568.271144] sshd[28872]: segfault at 7f10e28ad660 ip 00007f10e28ad660 sp 00007ffc198b36a8 error 14 in pam_env.so[7f30de510000+3000] [9493237.396986] shinken-poller[17016]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007fffbe36cbe8 error 4 in python2.7[400000+31e000] [9493251.923045] shinken-poller[17101]: segfault at 7fadb31e18f8 ip 00000000004a6fb0 sp 00007ffe8da8c4d8 error 4 in python2.7[400000+31e000] [9493256.621800] shinken-poller[17159]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007fff85627848 error 4 in python2.7[400000+31e000] [9493264.357160] shinken-poller[17255]: segfault at 200c6d5a0 ip 00000000004a6008 sp 00007fff3ed0dd60 error 4 in python2.7[400000+31e000] [9493265.737436] shinken-poller[17302]: segfault at 7f4d1684b000 ip 000000000049b3db sp 00007fff61565b88 error 4 in python2.7[400000+31e000] [9493265.740622] shinken[17267]: segfault at 7f96ffb91fc0 ip 00007f96ffb91fc0 sp 00007ffec00e6ef8 error 14 [9493266.779689] shinken-poller[17349]: segfault at 7fb1745bc6c0 ip 000000000049a144 sp 00007ffc390e7ae0 error 6 in python2.7[400000+31e000] [9493268.039805] shinken-poller[17398]: segfault at 200093bb68 ip 00000000004b11cc sp 00007ffc84589600 error 4 in python2.7[400000+31e000] [9493317.371962] shinken-poller[17443]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007ffcbf5d4318 error 4 in python2.7[400000+31e000] [10142463.472313] certbot[27552]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007ffc9b39cb58 error 4 in python2.7[400000+31e000] [10152361.563367] rsync[28972]: segfault at 7fe5e34a2a10 ip 00007fe5e34a2a10 sp 00007ffe40f924f8 error 14 [10152368.833664] shinken-poller[21692]: segfault at 7f773c5d6620 ip 00007f573c2ad000 sp 00007ffd3b27bb80 error 6 in libc-2.19.so[7f573c231000+1a1000] [10152370.354746] printf[28995]: segfault at 7f27db0a2610 ip 00007f25dad78fd0 sp 00007ffe0efe54d0 error 4 in libc-2.19.so[7f25dacfd000+1a1000] [10152377.771294] shinken-poller[21700]: segfault at 7f773c5d68c0 ip 00007f573c2aae0d sp 00007ffd3b27b6f0 error 4 in libc-2.19.so[7f573c231000+1a1000]
Merci :)
Ce sont des extraits que tu as coupé ? Car vu les temps entre les timestamp et le nombre, pour l'instant rien ne justifie de chercher quoi que ce soit ici.
Ça peut aussi bien correspondre à de la majorité de lib sauvage dans une faille quantique entre installation et génération des liens symboliques.
ou un milliers d'autres choses.
- Colin J. βrigato - ¥ngénieur Σystème & Δirecteur de Projet ✆ 06 43 19 33 49
On 4 Jun 2017, 11:06, at 11:06, Alarig Le Lay alarig@swordarmor.fr wrote:
Bonjour,
Je viens de me rendre compte qu’une machine a de nombreux segfaults. Et évidemment je n’ai pas d’accès KVM/IP pour lancer un memtest… Vous auriez des outils pour gérer ce genre de cas ?
alarig@argall:~$ dmesg | grep segfault [8797847.703324] dpkg-preconfigu[12044]: segfault at 2000000008 ip 00007f8bb83ef530 sp 00007ffc308e5140 error 4 in libperl.so.5.20.2[7f8bb8331000+1b7000] [8797847.778480] dpkg[12046]: segfault at 2014ff946 ip 000000000040c02e sp 00007ffcf2019260 error 4 in dpkg[400000+42000] [8797902.719319] apt-get[12169]: segfault at 7f23b2d8ab48 ip 00007f03b4cfc1f9 sp 00007ffdd28b1b50 error 4 in libapt-pkg.so.4.12.0[7f03b4c3c000+168000] [8797916.087786] check_ftp[12206]: segfault at 7f7ba434afb8 ip 00007f79a402de33 sp 00007ffdbcdfbbb8 error 4 in libc-2.19.so[7f79a3fa8000+1a1000] [8797916.411782] check_http[12207]: segfault at 7f2a7cee5e48 ip 00007f0a7e358ce9 sp 00007ffece6adea0 error 4 in ld-2.19.so[7f0a7e34b000+20000] [8797920.268743] shinken-poller[18153]: segfault at 2000944640 ip 00000000004b641c sp 00007ffcb1232750 error 6 in python2.7[400000+31e000] [8797945.537473] shinken-poller[12228]: segfault at 7f432541d9d8 ip 000000000049ab62 sp 00007ffcb1232e60 error 4 in python2.7[400000+31e000] [8797947.132438] check_smtp[12331]: segfault at 7f866f1109c8 ip 00007f846e24cb3e sp 00007ffe2da427b0 error 4 in libpthread-2.19.so[7f846e246000+18000] [8797949.144224] shinken-poller[18137]: segfault at 7f430563a6a8 ip 000000000049f6c3 sp 00007ffcb1232ab0 error 4 in python2.7[400000+31e000] [8797965.240866] check_http[12364]: segfault at 7f89b3cda087 ip 00007f8bb47508f0 sp 00007ffe765748f8 error 4 in ld-2.19.so[7f8bb4739000+20000] [8797965.248510] check_imap[12365]: segfault at 7fdbaa16aff0 ip 00007ffba87a2495 sp 00007ffd03a09cb8 error 4 in libc-2.19.so[7ffba869b000+1a1000] [8797965.294364] shinken-poller[12342]: segfault at 7f612541d060 ip 00000000004e43ef sp 00007ffcb1232940 error 4 in python2.7[400000+31e000] [9423564.685198] shinken-poller[28853]: segfault at 200093beb0 ip 00000000004a0c02 sp 00007ffcb1231b90 error 6 in python2.7[400000+31e000] [9423564.686052] shinken-poller[12372]: segfault at 200093beb0 ip 00000000004ed8c4 sp 00007ffcb1232f20 error 6 in python2.7[400000+31e000] [9423565.975707] shinken-poller[18037]: segfault at 7f612541d060 ip 00000000004e43ef sp 00007f631e536900 error 4 in python2.7[400000+31e000] [9423568.271144] sshd[28872]: segfault at 7f10e28ad660 ip 00007f10e28ad660 sp 00007ffc198b36a8 error 14 in pam_env.so[7f30de510000+3000] [9493237.396986] shinken-poller[17016]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007fffbe36cbe8 error 4 in python2.7[400000+31e000] [9493251.923045] shinken-poller[17101]: segfault at 7fadb31e18f8 ip 00000000004a6fb0 sp 00007ffe8da8c4d8 error 4 in python2.7[400000+31e000] [9493256.621800] shinken-poller[17159]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007fff85627848 error 4 in python2.7[400000+31e000] [9493264.357160] shinken-poller[17255]: segfault at 200c6d5a0 ip 00000000004a6008 sp 00007fff3ed0dd60 error 4 in python2.7[400000+31e000] [9493265.737436] shinken-poller[17302]: segfault at 7f4d1684b000 ip 000000000049b3db sp 00007fff61565b88 error 4 in python2.7[400000+31e000] [9493265.740622] shinken[17267]: segfault at 7f96ffb91fc0 ip 00007f96ffb91fc0 sp 00007ffec00e6ef8 error 14 [9493266.779689] shinken-poller[17349]: segfault at 7fb1745bc6c0 ip 000000000049a144 sp 00007ffc390e7ae0 error 6 in python2.7[400000+31e000] [9493268.039805] shinken-poller[17398]: segfault at 200093bb68 ip 00000000004b11cc sp 00007ffc84589600 error 4 in python2.7[400000+31e000] [9493317.371962] shinken-poller[17443]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007ffcbf5d4318 error 4 in python2.7[400000+31e000] [10142463.472313] certbot[27552]: segfault at 2000000008 ip 00000000004a6fb0 sp 00007ffc9b39cb58 error 4 in python2.7[400000+31e000] [10152361.563367] rsync[28972]: segfault at 7fe5e34a2a10 ip 00007fe5e34a2a10 sp 00007ffe40f924f8 error 14 [10152368.833664] shinken-poller[21692]: segfault at 7f773c5d6620 ip 00007f573c2ad000 sp 00007ffd3b27bb80 error 6 in libc-2.19.so[7f573c231000+1a1000] [10152370.354746] printf[28995]: segfault at 7f27db0a2610 ip 00007f25dad78fd0 sp 00007ffe0efe54d0 error 4 in libc-2.19.so[7f25dacfd000+1a1000] [10152377.771294] shinken-poller[21700]: segfault at 7f773c5d68c0 ip 00007f573c2aae0d sp 00007ffd3b27b6f0 error 4 in libc-2.19.so[7f573c231000+1a1000]
Merci :)
alarig
Liste de diffusion du FRsAG http://www.frsag.org/
On dim. 4 juin 11:12:03 2017, Colin Brigato wrote:
Ce sont des extraits que tu as coupé ? Car vu les temps entre les timestamp et le nombre, pour l'instant rien ne justifie de chercher quoi que ce soit ici.
Ça peut aussi bien correspondre à de la majorité de lib sauvage dans une faille quantique entre installation et génération des liens symboliques.
ou un milliers d'autres choses.
- Colin J. βrigato - ¥ngénieur Σystème & Δirecteur de Projet ✆ 06 43 19 33 49
Non, c’est la sortie brute de la commande. Et j’ai jamais vu autant de segfaults en random sur un serveur, surtout quand rien n’est compilé à la main. Surtout sur des trucs comme sshd ou printf…
On m’a conseillé memtester en offlist, ça donne ça :
root@argall:~# memtester 7066669056B memtester version 4.3.0 (64-bit) Copyright (C) 2001-2012 Charles Cazabon. Licensed under the GNU General Public License version 2 (only).
pagesize is 4096 pagesizemask is 0xfffffffffffff000 want 6739MB (7066669056 bytes) got 6739MB (7066669056 bytes), trying mlock ...locked. Loop 1: Stuck Address : testing 0FAILURE: possible bad address line at offset 0xf58ca000. Skipping to next test... Random Value : FAILURE: 0x6b775b1413a73efb != 0x6b775b3413a73efb at offset 0x22f24000. FAILURE: 0x7dbd93e3fbdf6891 != 0x7dbd93c3fbdf6891 at offset 0x22f24010. FAILURE: 0xf17dc2c4ffb758fa != 0xf17dc2c6ffb758fa at offset 0x22f24018. FAILURE: 0xeffbe1ec3fdd9f59 != 0xeffbe1ee3fdd9f59 at offset 0x22f24020. FAILURE: 0x5f5e39ca5fbf89ba != 0x5f5e39c85fbf89ba at offset 0x22f24028. FAILURE: 0x5dcb7ca3fdff6569 != 0x5dcb7ca1fdff6569 at offset 0x22f24030. FAILURE: 0xceffd2c17dd391e5 != 0xceffd2e17dd391e5 at offset 0x22f24078. […]
Je crois que je suis bon pour demander un changement de RAM :)
Si ton système le supporte, tu peux toujours installer les "edac-utils", ils pourront te dire quelle barrette cause tout ce bazar.
Par contre, après constatation, fait un "rmmod edac", car sinon ce sont tes disques durs qui vont morfler :).
++
On 4 June 2017 12:12:26 CEST, Alarig Le Lay alarig@swordarmor.fr wrote:
On m’a conseillé memtester en offlist, ça donne ça :
root@argall:~# memtester 7066669056B memtester version 4.3.0 (64-bit) Copyright (C) 2001-2012 Charles Cazabon. Licensed under the GNU General Public License version 2 (only).
pagesize is 4096 pagesizemask is 0xfffffffffffff000 want 6739MB (7066669056 bytes) got 6739MB (7066669056 bytes), trying mlock ...locked. Loop 1: Stuck Address : testing 0FAILURE: possible bad address line at offset 0xf58ca000. Skipping to next test... Random Value : FAILURE: 0x6b775b1413a73efb != 0x6b775b3413a73efb at offset 0x22f24000. FAILURE: 0x7dbd93e3fbdf6891 != 0x7dbd93c3fbdf6891 at offset 0x22f24010. FAILURE: 0xf17dc2c4ffb758fa != 0xf17dc2c6ffb758fa at offset 0x22f24018. FAILURE: 0xeffbe1ec3fdd9f59 != 0xeffbe1ee3fdd9f59 at offset 0x22f24020. FAILURE: 0x5f5e39ca5fbf89ba != 0x5f5e39c85fbf89ba at offset 0x22f24028. FAILURE: 0x5dcb7ca3fdff6569 != 0x5dcb7ca1fdff6569 at offset 0x22f24030. FAILURE: 0xceffd2c17dd391e5 != 0xceffd2e17dd391e5 at offset 0x22f24078. […]
Je crois que je suis bon pour demander un changement de RAM :)
-- alarig
On dim. 4 juin 15:17:24 2017, Cyril LAVIER wrote:
Si ton système le supporte, tu peux toujours installer les "edac-utils", ils pourront te dire quelle barrette cause tout ce bazar.
Par contre, après constatation, fait un "rmmod edac", car sinon ce sont tes disques durs qui vont morfler :).
D’après dmidecode, il n’y a qu’une barrette dans la machine. Mais je note la commande, ça pourra toujours me servir un de ces quatre :)
-
Alarig Le Lay -
Colin Brigato -
Cyril LAVIER