enterprise-support team mailing list archive

[Robin Kluth <question698847@xxxxxxxxxxxxxxxxxxxxx>]

New question #698847 on openldap in Ubuntu:
https://answers.launchpad.net/ubuntu/+source/openldap/+question/698847

Hi,

My system: 

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:        18.04
Codename:       bionic

slapd: 2.4.45+dfsg-1ubuntu1.10

I've configured slapd to use the meta backend with multiple domains. However, I noticed, that as soon as one uri is down (due to whatever reason) the whole application (that slapd is used in) stop working. Stop working means: no login or ldap searches are possible.

Example: I use this slapd "proxy" in nextcloud. As soon as one uri is down, no one can login anymore (user is stored in another domain which is online).

ldp.exe shows me, that slapd is actually returning all results - except from the one uri which is off.

So I tried to set onerr - its default is continue, which sounds reasonable. However, setting every other option (report, stop) does not step into effect at all.

ldp.exe always return the results alongside with the timeout error. And I believe this is, what the end-application sees: an ldap error. And then their own ldap error handling takes place.

Question: is there an issue with my onerr usage or is it a "bug"?


I tried setting onerr after "database meta" and even tried to set it for every uri-block - no difference.

Current config: https://pastebin.com/VRTJPGQq

Thanks in advance!

-- 
You received this question notification because your team Ubuntu
Server/Client Support Team is an answer contact for openldap in Ubuntu.