[Freeipa-users] ns-slapd started crashing suddenly

[Lukas Slebodnik]

On (05/06/15 07:35), Rich Megginson wrote:
>On 06/05/2015 03:40 AM, Dawid Rabiega wrote:
>>Hi,
>>One of my ipa server on fedora 19 since yesterday started to crash, with
>>following message to dmesg:
>>
>>$ dmesg | tail -n 20
>>[6706148.291648] ns-slapd[3212]: segfault at 0 ip 00007f6fc9a84421 sp
>>00007f6f8f7eb928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f6fc99fe000+1b6000]
>>[6706170.887926] ns-slapd[3359]: segfault at 0 ip 00007f923ce89421 sp
>>00007f91fd7e7928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f923ce03000+1b6000]
>>[6706264.491787] ns-slapd[3463]: segfault at 0 ip 00007f2d9020d421 sp
>>00007f2d527e9928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f2d90187000+1b6000]
>>[6706311.092133] ns-slapd[4015]: segfault at 0 ip 00007f62287d7421 sp
>>00007f61efff4928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f6228751000+1b6000]
>>[6706500.581441] ns-slapd[4361]: segfault at 0 ip 00007facbe1e1421 sp
>>00007fac807e5928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7facbe15b000+1b6000]
>>[6706690.693958] ns-slapd[4932]: segfault at 0 ip 00007f8d72cbc421 sp
>>00007f8d3d7f7928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f8d72c36000+1b6000]
>>[6715473.156094] ns-slapd[18406]: segfault at 0 ip 00007f22fedea421 sp
>>00007f22c1fe8928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f22fed64000+1b6000]
>>[6716455.653949] ns-slapd[20571]: segfault at 0 ip 00007f190695e421 sp
>>00007f18dcff6928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f19068d8000+1b6000]
>>[6716646.006961] ns-slapd[21375]: segfault at 0 ip 00007ffb9c889421 sp
>>00007ffb64ff6928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7ffb9c803000+1b6000]
>>[6717027.574362] ns-slapd[22082]: segfault at 0 ip 00007f9fdbda7421 sp
>>00007f9faeffa928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f9fdbd21000+1b6000]
>>[6751004.788596] ns-slapd[9779]: segfault at 0 ip 00007f0398f48421 sp
>>00007f03617f7928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f0398ec2000+1b6000]
>>[6751019.360517] ns-slapd[10018]: segfault at 0 ip 00007f267852c421 sp
>>00007f263afea928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f26784a6000+1b6000]
>>[6751154.258362] ns-slapd[10179]: segfault at 0 ip 00007f2c6d854421 sp
>>00007f2c31ff0928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f2c6d7ce000+1b6000]
>>[6751208.966127] ns-slapd[10520]: segfault at 0 ip 00007f9a31a59421 sp
>>00007f99f87ed928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f9a319d3000+1b6000]
>>[6751305.469969] ns-slapd[10608]: segfault at 0 ip 00007f6e9348b421 sp
>>00007f6e55ff0928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f6e93405000+1b6000]
>>[6751328.997404] ns-slapd[10736]: segfault at 0 ip 00007f8c936b1421 sp
>>00007f8c5d7f7928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f8c9362b000+1b6000]
>>[6751432.356753] ns-slapd[10835]: segfault at 0 ip 00007f7dffd84421 sp
>>00007f7dca7f9928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f7dffcfe000+1b6000]
>>[6751454.826551] ns-slapd[11107]: segfault at 0 ip 00007f03621d5421 sp
>>00007f0326fea928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f036214f000+1b6000]
>>[6751549.459424] ns-slapd[11414]: segfault at 0 ip 00007f9e0f74b421 sp
>>00007f9dd2fea928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f9e0f6c5000+1b6000]
>>[6751573.611284] ns-slapd[11567]: segfault at 0 ip 00007f044fd73421 sp
>>00007f0419ff8928 error 4 in libc-2.17.so
>><http://libc-2.17.so/>[7f044fced000+1b6000]
>>
>>$ rpm -qa | grep 389
>>389-ds-base-1.3.1.22-1.fc19.x86_64
>>389-ds-base-libs-1.3.1.22-1.fc19.x86_
>>
>>$ rpm -qa | grep ipa
>>libipa_hbac-python-1.11.5.1-1.fc19.x86_64
>>sssd-ipa-1.11.5.1-1.fc19.x86_64
>>freeipa-client-3.3.5-1.fc19.x86_64
>>freeipa-admintools-3.3.5-1.fc19.x86_64
>>freeipa-server-3.3.5-1.fc19.x86_64
>>python-iniparse-0.4-7.fc19.noarch
>>libipa_hbac-1.11.5.1-1.fc19.x86_64
>>freeipa-python-3.3.5-1.fc19.x86_64
>>
>>I have no idea what happened, and what check next. Any idea?
>
>We'll need to get a core, and see a good stacktrace from the core.
>http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes
>Since this is IPA, you'll need to
>
># debuginfo-install 389-ds-base ipa-server slapi-nis
>
Fedora 19 is not supported since 2015-01-06

Could you try to test with fedora 20?
It might be possible that bug is already fixed in newer versions.

LS