https://bz.apache.org/bugzilla/show_bug.cgi?id=63305
--- Comment #2 from Martin Fúsek <mfu...@newps.cz> ---
(In reply to Christophe JAILLET from comment #1)
> This has been fixed in trunk in r1856735.
>
> The patch is different from the one attached in this PR.
> Could you please test and confirm that it solves the issue for you as well?
Yes it works. But in trunk revision 1831165: "mod_ldap: log and abort locking
errors. related to PR60296 investigation RMM corruption is really nasty, so
abort on locking failures" make it also broken. Without revision
1831165(commenting out if (rv != APR_SUCCESS) {) it works OK. Problem is that
some request probably arrive after lock cleanup (after reload) and assertion
fail (new lock on cache cleanup works ok).
CoreDumpDirectory /tmp/
#LDAPLibraryDebug 7
LDAPLibraryDebug disabled
LDAPConnectionPoolTTL 15
LDAPSharedCacheSize 10485760
LDAPCacheEntries 10240
LDAPCacheTTL 600
LDAPOpCacheEntries 10240
LDAPOpCacheTTL 600
LDAPVerifyServerCert Off
<Location /ldap-status>
SetHandler ldap-status
Require host 127.0.0.1
</Location>
<Location />
AuthName "ISDS - DS"
AuthLDAPBindDN "<redacted>"
AuthLDAPBindPassword "<redacted>"
AuthType basic
AuthBasicProvider ldap
AuthLDAPRemoteUserIsDN on
<LimitExcept OPTIONS>
Require valid-user
</LimitExcept>
AuthLDAPURL ldap://172.24.40.126/ou=test,o=test?cn,isdsRights?sub? TLS
</Location>
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
