Thanks. Will get the debug info established on all of our servers. I was looking for this info and didn't realize it was buried in the FAQ. May I suggest the Debugging item be added to the HowTo list or some place more prominent so it is easier to find? /mrg On Oct 2, 2013, at 10:32 AM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote: > On 10/02/2013 08:22 AM, Michael Gettes wrote: >> We had a crash early this morning on one of our masters (MMR with 2 servers, 3 replicas connected to each). Nothing in the errors log. The service was restarted and has not crashed since. >> >> From syslog we have: >> >> kernel: ns-slapd[18143]: segfault at 0 ip 00007f43d5eeaad6 sp 00007f437dbedf38 error 4 i >> >> on the live process: >> >> 0x00007f43d5eeaad6 - 0x7f43d5dc3000 = 0x127ad6 >> >> 0000000000127ac0 <__strcmp_sse42>: >> 127ac0: 89 f1 mov %esi,%ecx >> 127ac2: 89 f8 mov %edi,%eax >> 127ac4: 48 83 e1 3f and $0x3f,%rcx >> 127ac8: 48 83 e0 3f and $0x3f,%rax >> 127acc: 83 f9 30 cmp $0x30,%ecx >> 127acf: 77 3f ja 127b10 <__strcmp_sse42+0x50> >> 127ad1: 83 f8 30 cmp $0x30,%eax >> 127ad4: 77 3a ja 127b10 <__strcmp_sse42+0x50> >> *127ad6: f3 0f 6f 0f movdqu (%rdi),%xmm1 >> >> Our environment consists of: >> >> 389-admin.x86_64 1.1.29-1.el6 installed >> 389-admin-console.noarch 1.1.8-1.el6 @epel-x86_64-server-6 >> 389-admin-console-doc.noarch 1.1.8-1.el6 @epel-x86_64-server-6 >> 389-adminutil.x86_64 1.1.15-1.el6 installed >> 389-console.noarch 1.1.7-3.el5 installed >> 389-ds.noarch 1.2.2-1.el6 @epel-x86_64-server-6 >> 389-ds-base.x86_64 1.2.11.15-22.el6_4 installed >> 389-ds-base-libs.x86_64 1.2.11.15-22.el6_4 installed >> 389-ds-console.noarch 1.2.6-1.el6 @epel-x86_64-server-6 >> 389-ds-console-doc.noarch 1.2.6-1.el6 @epel-x86_64-server-6 >> 389-dsgw.x86_64 1.1.10-1.el6 @epel-x86_64-server-6 >> 389-admin.i686 1.1.29-1.el6 epel-x86_64-server-6 >> 389-adminutil.i686 1.1.15-1.el6 epel-x86_64-server-6 >> 389-adminutil-devel.i686 1.1.15-1.el6 epel-x86_64-server-6 >> 389-adminutil-devel.x86_64 1.1.15-1.el6 epel-x86_64-server-6 >> 389-ds-base-debuginfo.x86_64 1.2.10.26-1.el6_3 389_rhel6_x86_64 >> 389-ds-base-devel.i686 1.2.11.15-22.el6_4 rhel-x86_64-server-optional-6 >> 389-ds-base-devel.x86_64 1.2.11.15-22.el6_4 rhel-x86_64-server-optional-6 >> 389-ds-base-libs.i686 1.2.11.15-22.el6_4 rhel-x86_64-server-6 >> >> uname -a >> Linux XXX 2.6.32-358.14.1.el6.x86_64 #1 SMP Mon Jun 17 15:54:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux >> >> I've looked around in trac and can't find anything obvious. Happy to report as a bug if this is sufficient info. > For crashes, we either need a reproducer, or we need http://port389.org/wiki/FAQ#Debugging_Crashes > >> >> /mrg >> -- >> 389 users mailing list >> 389-users@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/389-users > -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
