Am Di., 7. Apr. 2020 um 08:56 Uhr schrieb Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de:
Kevin Olbrich ko@sv01.de schrieb am 06.04.2020 um 23:00 in Nachricht
<15853_1586208569_5E8B9F39_15853_1729_1_CA+gLzy8cpURhV3Ti41im3Z=vRcq2VoEd0n_E+P8 EKnfN4=wPQ@mail.gmail.com>:
Hi!
I'm experiencing an issue with Slapd 2.4.49 on Debian Buster. I use Slapd as a proxy / lb with two AD nodes behind it.
If I reboot one of the AD nodes, everything is fine. As soon as I reboot the seconds one (while the first is back and available), OpenLDAP shuts down immediately: Apr 06 22:03:33 ldap-lb1.ldap.example.com slapd[22140]: Stopping OpenLDAP: slapd. Apr 06 22:03:33 ldap-lb1.ldap.example.com systemd[1]: slapd.service: Succeeded.
There is no traffic during this time and it matches the exact time when node two is down.
Debian still uses an init script for slapd but I did not find anything interesting in it.
Is there a config setting that I missed in the docs that explains this behavior? As it's not crashing, HA in systemd won't catch this issue.
Start some tracing and logging I'd suggest. Something ust be triggering that, and you must capture the "something" before you can get a solution.
I already did with loglevel 256. I can see a bind request from a user who wants to search a user. There is no error in the log. It just shuts down when the first node is back online and the second one reboots (1h between both reboots).
Browsing the docs and mailinglist I noticed that I'm not the only one with such an issue. A lot of Zimbra users had this in the past, all without any error in their logs.
For me it looks like Slapd shuts down when no backend is available to proxy requests to, because it does not detect the first node as being back online.
Kind regards Kevin