Daca e hardware, urmeaza un kernel panic curand si atunci vom fi siguri.
2016-01-19 12:09 GMT+02:00 manuel "lonely wolf" wolfshant <[email protected] >: > On 01/19/2016 11:31 AM, Sorin Vijelie wrote: > > On Mon, 2016-01-18 at 11:40 +0200, manuel "lonely wolf" wolfshant wrote: > >> On 01/18/2016 11:32 AM, Sorin Vijelie wrote: > >>> Salut, > >>> > >>> Se da un Centos 7. Din senin, nu ma mai pot loga nici pe ssh, nici > >>> local, nici pe pop3/smtp. Pot intra in single mode. > >>> > >>> Sugestii ? > >> vezi ce erori apar in loguri. > > /var/log/messages > > > > 15:30:01 kernel: crond[747]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 > > 15:30:01 kernel: crond[748]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 in pam_deny.so[7f3389ac0000+1000] > > 15:30:01 kernel: crond[746]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 > > 15:30:01 kernel: crond[740]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 in pam_deny.so[7f3389ac0000+1000] > > 15:30:01 kernel: crond[743]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 in pam_deny.so[7f3389ac0000+1000] > > 15:30:01 kernel: crond[741]: segfault at 0 ip (null) sp > > 00007ffddc887788 error 14 in pam_deny.so[7f3389ac0000+1000] > > 15:30:01 kernel: crond[750]: segfault at 0 ip (null) sp sp > > 00007ffe93c5cec8 error 14 in libnss_files-2.17.so[7f69ab799000+c000] > > 15:34:02 kernel: crond[2347]: segfault at 0 ip (null) sp > > 00007ffcff9bcc18 error 14 in pam_deny.so[7fe926b6c000+1000] > > 15:34:06 kernel: saslauthd[704]: segfault at 0 ip (null) sp > > 00007fff2f845b68 error 14 in libfreeblpriv3.so[7fb616da4000+79000] > > 15:34:16 kernel: auth[2298]: segfault at 0 ip (null) sp > > 00007ffdb7980158 error 14 in libnss_files-2.17.so[7f5b6a566000+c000] > > 15:34:23 kernel: saslauthd[706]: segfault at 0 ip (null) sp > > 00007fff2f845b68 error 14 in libfreeblpriv3.so[7fb616da4000+79000] > > 15:34:25 kernel: saslauthd[707]: segfault at 0 ip (null) sp > > > > > > > >> ps: "din senin" nu exista. > > Incercam sa spun ca n-am facut nici o modificare in ultimele saptamani. > > > > Am testat RAM-ul si pare ok. > decizie corecta. doar ca din pacate > a) testele de memorie trebuie lasate sa se desfasoare, pot sa nu > detecteze problemele din prima; stiu de cazuri in care memoria defecta > nu s-a manifestat decit dupa >20 de cicluri complete. Un american > popvestea pe freenode ca a lasat o memorie in teste 5 zile ( era ferm > convins ca e defecta dar nu avea dovada certa si avea si timp ) pina > cind memtest86+ a tipat > b) chiar mie mi s-a intimplat ca un modul defect sa nu fie detectat > atita timp cit masina rula in dual channel. in clipa cind am scos unul > dintre module, celalalt a fost instantaneu detectat drept defect. > in plus genul asta de erori poate insemna si racire defectuoasa ( a > procesorului in special dar si la nivel de chipset al placii de baza ). > > > > > > > > Suficient de dubios, prin urmare am reinstalat. > > avind in vedere ca erau multiple aplicatii care dadeau segfault eu > banuiesc in continuare ca e un defect hardware. > _______________________________________________ > RLUG mailing list > [email protected] > http://lists.lug.ro/mailman/listinfo/rlug > -- Main OS Architect at Project RoGentos (Romanian Gentoo Operating Systems) Group. Based on Sabayon and Gentoo Linux, Kogaion GNU/Linux and Argent GNU/Linux tend to offer support mainly for all Romanian Linux users and entrepreneurs which seek to learn an open and free system based on true values :) http://rogentos.ro www.facebook.com/RogentosLinux https://plus.google.com/106559511636021124919/ Google+ _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
