https://bugs.openldap.org/show_bug.cgi?id=10087
Issue ID: 10087
Summary: slapd crashes with core dump Assertion
`!LDAP_BACK_CONN_TAINTED( lc )
Product: OpenLDAP
Version: 2.5.15
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: b...@openldap.org
Reporter: rajko@albrecht.jetzt
Target Milestone: ---
The slapd daemon crashes every ten minutes with
slapd: ../../../../../servers/slapd/back-ldap/bind.c:181:
ldap_back_conn_delete: Assertion `!LDAP_BACK_CONN_TAINTED( lc )' failed.
Aborted (core dumped)
I searched around for multiple days but didn't find any solution to this
problem.
I have the same problem with 2.6.x versions.
It is configured to act as caching ldap, while multiple hundred systems contact
it.
The error message is completely useless for sysadmins because they don't
understand what this means for them (as said, asking search engines gives no
answers) nor I don't know if - and if so how - I can fix this with
configuration.
I don't see if this message is talking about the connection to the upstream
ldap server or if this is the connection from a client to the caching (and
crashing) daemon.
First setup was plain on a linux machine, now runnig inside docker environment
so the service is restarted after the crash. This is of course not a nice
solution.
And it looks like the same like #4390 which is marked as "not solved".
At least a description what this error messages means would be very helpful
incl. how a workaround could look like (increasing timeouts, increase/decrease
a socket pool or whatever).
Currently the slapd is nearly useless when using it as a caching ldap with high
load.
Any hints?
--
You are receiving this mail because:
You are on the CC list for the issue.
