Bug 448900
| Summary: | SIGSEGV in a search | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] 389 | Reporter: | Paulo Alberto <pauloviolada> | ||||||
| Component: | Directory Server | Assignee: | Rich Megginson <rmeggins> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Orla Hegarty <ohegarty> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 1.1.0 | CC: | nkinder | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-06-24 17:01:07 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Paulo Alberto
2008-05-29 12:53:34 UTC
Created attachment 307046 [details]
Strace from crash.
OS: RHEL5 What is the search? Base, scope, filter, attribute list? Can you post excerpts from the access or error log around the time of the crash? Could this be related to the substring filter problem? I did not post it because it appears in the strace file. But there it is: Search (from access log): [29/May/2008:09:34:04 -0300] conn=2722 op=1 SRCH base="o=XXXXXXXXXXXX" scope=2 filter="(&(|(objectClass=inetorgperson)(objectClass=posixaccount)(objectClass=groupOfUniqueNames))(|(cn=*Macintosh*)(mail=*Macintosh*)))" attrs="uidNumber uid cn givenName sn audio description labeledUri o ou title street l st postalCode telephoneNumber homePhone facsimileTelephoneNumber mobile pager mail roomNumber jpegPhoto displayName postalAddress userSMIMECertificate birthDate note carPhone primaryPhone category businessRole assistantPhone assistantName fileAs homeFacsimileTelephoneNumber freeBusyURI calendarURI otherPhone callbackPhone entryuuid uid uidNumber objectClass createTimestamp modifyTimestamp creatorsName modifiersName objectClass" Error log does not show nothing. I don't think this could be related to the substring filter problem. The other problem was because the search filter was too long, but it is not this case. Thanks. This search does use a substring filter, but as you say, it is small. How many entries should match this filter? Have you been able to get a consistently reproducible test case? Have you been able to get a core with stack trace? This matches only one entry. Unfortunately I have not been able to reproduce it yet, but I'm still trying. Yesterday there was another crash, with the same search style, but that does not match any entry: [28/May/2008:15:30:42 -0300] conn=192298 op=1 SRCH base="o=XXXXXXXXX" scope=2 filter="(&(|(objectClass=inetorgperson)(objectClass=posixaccount)(objectClass=groupOfUniqueNames))(|(sn=*uilsom*)(givenName=*uilsom*)(o=*uilsom*)(ou=*uilsom*)(description=*uilsom*)(mail=*uilsom*)))" attrs="uidNumber uid cn givenName sn audio description labeledUri o ou title street l st postalCode telephoneNumber homePhone facsimileTelephoneNumber mobile pager mail roomNumber jpegPhoto displayName postalAddress userSMIMECertificate birthDate note carPhone primaryPhone category businessRole assistantPhone assistantName fileAs homeFacsimileTelephoneNumber freeBusyURI calendarURI otherPhone callbackPhone entryuuid uid uidNumber objectClass createTimestamp modifyTimestamp creatorsName modifiersName objectClass" I don't know if strace helps, but it's attached. Sorry, but I don't know how to get a core with strack trace. I will try to learn and send it. Created attachment 307101 [details]
Another strace from the crash.
strace is usually no good with a crash since strace only shows system calls and crashes are usually in our code :P # gdb /usr/sbin/ns-slapd /path/to/core.pid (gdb) bt This will print out the stack trace I'm going to mark this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=182621 - please reopen if you feel this is not correct. *** This bug has been marked as a duplicate of 182621 *** |