Issue 6928 - slapd: daemon.c:942: slapd_clr_write: Assertion `((slap_daemon[id].sd_index[(s)]) != -1)' failed.
Summary: slapd: daemon.c:942: slapd_clr_write: Assertion `((slap_daemon[id].sd_index[(...
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.25
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-05 10:41 UTC by Michael Ströder
Modified: 2017-04-12 20:29 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Michael Ströder 2011-05-05 10:41:39 UTC
Full_Name: Michael Str�der
Version: 2.4.25
OS: 
URL: 
Submission from: (NULL) (195.145.144.134)


slapd (serving as provider) crashes from time to time (several times today!)
when a consumer has some problems. I suspect this is related to ITS#6922 and
therefore I suspect that Howard's answer is again just "there is no issue".

The last lines in the logs always show that the consumer already sent an UNBIND
and after that slapd dies with this failed assertion.

conn=1090 op=1 INTERM oid=1.3.6.1.4.1.4203.1.9.1.4
conn=1090 op=2 UNBIND
conn=1090 fd=112 closed
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
connection_read(112): no connection!
slapd: daemon.c:942: slapd_clr_write: Assertion
`((slap_daemon[id].sd_index[(s)]) != -1)' failed.
/infraldap/sbin/start-slapd.sh: line 16: 28888 Aborted                
${OPENLDAP_PREFIX}/libexec/slapd -h "ldap://0.0.0.0:389 ldaps://0.0.0.0:636
ldapi://%2ftmp%2finfraldap-socket????x-mod=0770" -d config,stats,stats2,sync -n
slapd-e2-infra-ldap -u openldap -g openldap -f ${SLAPD_CONF}


Comment 1 Michael Ströder 2011-05-05 10:58:26 UTC
The root cause in this case is that the schema differs on the consumer and
schema violation errors were logged at the consumer. Obviously this is a
configuration error but the provider should not crash because of this!


Comment 2 Michael Ströder 2012-01-24 23:32:27 UTC
This might be a dup of ITS#7113.

Comment 3 Quanah Gibson-Mount 2012-01-26 19:37:40 UTC
changed notes
Comment 4 Quanah Gibson-Mount 2017-04-12 20:29:17 UTC
Hi Michael,

I'm going to assume this issue was fixed in 2.4.29 with the fix for 
ITS#7113.  If that's not the case, please follow up.  I will close this ITS 
in the meantime.

Regards,
Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>


Comment 5 OpenLDAP project 2017-04-12 20:29:25 UTC
duplicate of 7113?
7113 fixed, closing
Comment 6 Quanah Gibson-Mount 2017-04-12 20:29:25 UTC
changed notes
changed state Open to Closed
moved from Incoming to Software Bugs