[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4136) test036-meta-concurrency: line 188: 1342 Segmentation fault

On Thu, 2005-11-03 at 11:13 +0000, hyc@symas.com wrote:

> I haven't seen that. But re: this crash, I see that slapd #1 SEGVs 
> because the op it is processing has already been placed on the free list 
> by slap_op_free(). Looking in slapd.1.log I would guess the op got 
> abandoned because there is a DISCONNECT message due to bad decoding:
> connection_close: deferring conn=3 sd=17
> <= send_search_entry: conn 3 exit.
>  DISCONNECT tag=120 err=2 text=decoding error
>  DISCONNECT tag=120 err=2 text=error decoding filter
> send_ldap_result: conn=3 op=5 p=3
> send_ldap_result: err=0 matched="" text=""
> send_ldap_response: msgid=6 tag=101 err=0
> ldap_err2string
> <= ldap_bv2dn(ou=people,dc=example,dc=com)=0 Success
> slap_listener_activate(7):
> I'll see what I can do about fixing this. I guess an Abandon test ought 
> to be able to reproduce the problem.

Yes, I've also noticed that most of the errors occur after a decoding
error.  So, all in all, it appears we have two issues: back-ldap/meta
somehow sending an incorrect request (but it apparently passes libldap
parsing...), and slapd's frontend erroneously handling this abnormal
condition.  Unfortunately, it only appears to occur under heavy load;
I'll try with more logging if I can understand what's going on at the
proxy's side (unless it's again an issue related to the per-thread
context getting somehow corrupted).


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497