Am Di., 7. Apr. 2020 um 23:18 Uhr schrieb Quanah Gibson-Mount quanah@symas.com:
--On Tuesday, April 7, 2020 11:36 PM +0200 Kevin Olbrich ko@sv01.de wrote:
Def. ANOM_ABEND: Triggered when a processes ends abnormally (with a signal that could cause a core dump, if enabled).
Looks like it's actually crashing but I don't think it's because of "slap_global_control: unrecognized control: 1.3.6.1.4.1.42.2.27.8.5.1" as I can see multiple lines before the crash.
Is it possible that Slapd crashed if it tries to proxy data to a node while it shuts down? Maybe a special case when bind was successful but query failes?
Hi Kevin,
What OpenLDAP Release are you running? I ask, because there was a fix that went into OpenLDAP 2.4.49 specifically for a crasher with back-ldap and controls:
https://bugs.openldap.org/show_bug.cgi?id=9076
Regards, Quanah
My version is 2.4.49+dfsg-2~bpo10+1 (buster-backports). Should be in there I think. I've now included ppolicy.schema to solve the issue. Tomorrow I will try if the issue is still present.
Thanks for your input!
Regards Kevin
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Wednesday, April 8, 2020 12:35 AM +0200 Kevin Olbrich ko@sv01.de wrote:
My version is 2.4.49+dfsg-2~bpo10+1 (buster-backports). Should be in there I think. I've now included ppolicy.schema to solve the issue. Tomorrow I will try if the issue is still present.
Ok. If it still crashes, the best thing to do would be to:
a) Install the debugging symbols package
b) Get a full backtrace under GDB from the running process at the time at which it segfaults.
c) Open a bug at https://bugs.openldap.org, include your configuration (minus any passwords) and the full backtrace in the bug report.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Le 07/04/2020 à 23:56, Quanah Gibson-Mount a écrit :
--On Wednesday, April 8, 2020 12:35 AM +0200 Kevin Olbrich ko@sv01.de wrote:
My version is 2.4.49+dfsg-2~bpo10+1 (buster-backports). Should be in there I think. I've now included ppolicy.schema to solve the issue. Tomorrow I will try if the issue is still present.
Ok. If it still crashes, the best thing to do would be to:
a) Install the debugging symbols package
b) Get a full backtrace under GDB from the running process at the time at which it segfaults.
c) Open a bug at https://bugs.openldap.org, include your configuration (minus any passwords) and the full backtrace in the bug report.
Hello,
we also have quite similar issue with back-meta, even in 2.4.49, see https://bugs.openldap.org/show_bug.cgi?id=9098
Maybe this issues are linked.
--On Wednesday, April 8, 2020 10:27 AM +0200 Clément OUDOT clement.oudot@worteks.com wrote:
Hello,
we also have quite similar issue with back-meta, even in 2.4.49, see https://bugs.openldap.org/show_bug.cgi?id=9098
Unfortunately there's no usable/actionable data in that ticket to proceed with as it lacks a full backtrace.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org