Hide Forgot
Created attachment 1112618 [details] full stack trace from 310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760 Description of problem: stack trace review request, will need summary change. apparent ns-slapd crash in RHEL 6.7 IPA context with 1.2.11.15-68.el6_7 I attached 2 stack traces, nearly the same, the long file names have some context information: sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.310-ccpp-2016-01-07-11-58-56-5760.2016-01-07-11.58.26-5760.txt sf.01534564.rhel67.389-ds-base-1.2.11.15-68.el6_7.ns-slapd.stacktrace.320-ccpp-2016-01-06-13-00-34-28822.txt there were some initial reports of ns-slapd "hang" in salesforce case number, but I seem to see crashes: Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-BS-BR-BSCH -i /var/run/dirsrv/slapd-BS-'. Program terminated with signal 11, Segmentation fault. #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 136 2: movl %edx, %eax Version-Release number of selected component (if applicable): RHEL 6.7 389-ds-base-1.2.11.15-68.el6_7 How reproducible: N/A Steps to Reproduce: 1. N/A 2. 3. Actual results: Expected results: Additional info:
Created attachment 1112619 [details] full stack trace from 320-ccpp-2016-01-06-13-00-34-28822.2016-01-06-13.00.34-28822
Build tested: 389-ds-base-1.2.11.15-73.el6.x86_64 [1] Created 4000 users: # ldclt -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 -b "ou=people,dc=example,dc=com" -I 68 -e add,commoncounter -e "object=posix_users.ldif,rdn=uid:[A=INCRNNOLOOP(0;3999;5)]" [2] Anonymous search with paged results: # ldapsearch -x -h localhost -b "dc=example,dc=com" -E "pr=1000/noprompt" -l 10000 "(&(objectClass=posixAccount)(uid=*)(uidNumber=*)(gidNumber=*))" <snip> # search result search: 5 result: 0 Success control: 1.2.840.113556.1.4.319 false MAUCAQAEAA== pagedresults: cookie= # numResponses: 4004 # numEntries: 4000 Server didn't hang. Marking as VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0737.html