Bug 41287 – LDAP sdb zone '...: ldap_result returned -1 - deprecated sdb:ldap implementation?

Bug 41287 - LDAP sdb zone '...: ldap_result returned -1 - deprecated sdb:ldap implementation?


Summary:	LDAP sdb zone '...: ldap_result returned -1 - deprecated sdb:ldap implementat...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	DNS
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-18 10:22 CEST by Philipp Hahn
Modified:	2019-01-03 07:23 CET (History)
CC List:	1 user (show)

See Also:	25138
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	4: Will affect most installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	API change, Error handling, Roadmap discussion, Troubleshooting
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2016-05-18 10:22:53 CEST

Since some time BIND reports an error in /var/log/daemon.log:
>May 16 15:36:33 xen12 named[17539]: LDAP sdb zone 'phahn.dev': ldap_result returned -1
>May 24 13:14:00 xen12 named[32407]: LDAP sdb zone 'phahn.dev': ldap_result returned -1
>May 24 13:25:57 xen12 named[32407]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>May 27 09:57:03 xen12 named[2254]: LDAP sdb zone 'phahn.dev': ldap_result returned -1
>May 27 11:20:14 xen12 named[2254]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>May 28 09:52:48 xen12 named[2248]: LDAP sdb zone '0.168.192.in-addr.arpa': ldap_result returned -1
>May 29 08:56:36 xen12 named[2278]: LDAP sdb zone '0.168.192.in-addr.arpa': ldap_result returned -1
>May 29 09:17:50 xen12 named[2278]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>Jun  3 09:29:35 xen12 named[2282]: LDAP sdb zone '0.168.192.in-addr.arpa': ldap_result returned -1
>Jun  3 10:10:26 xen12 named[2282]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>Jun  4 09:10:06 xen12 named[2242]: LDAP sdb zone 'phahn.dev': ldap_result returned -1
>Jun  4 10:06:11 xen12 named[2242]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>Jun  5 10:11:36 xen12 named[2242]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>Jun  5 10:30:16 xen12 named[2242]: LDAP sdb zone '0.168.192.in-addr.arpa': ldap_result returned -1
>Jun  7 09:37:21 xen12 named[2207]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1
>Jun 10 10:09:44 xen12 named[2242]: LDAP sdb zone '0.168.192.in-addr.arpa': ldap_result returned -1
>Jun 10 10:37:29 xen12 named[2242]: LDAP sdb zone '17.200.10.in-addr.arpa': ldap_result returned -1

/etc/runit/univention-bind/supervise/pid:17539

I've also seen that at a customer system Ticket #2016050421000441

I was able to trigger the error doing
# dig @localhost -p 7777 -t axfr phahn.dev.
> May 18 10:10:15 xen12 named[17539]: LDAP sdb zone 'phahn.dev': ldap_result returned -1
> May 18 10:10:15 xen12 named[17539]: client ::1#55856: transfer of 'phahn.dev/IN': AXFR started
> May 18 10:10:15 xen12 named[17539]: client ::1#55856: transfer of 'phahn.dev/IN': AXFR ended

Nevertheless the transfer succeeded.


UCS is still using the (deprecated/unmaintained) sdb:ldap implementation, which has known multi-threading issues: <http://technik.blogs.nde.ag/2012/08/16/sdbldap-linux-named-accessing-openldap-is-not-thread-safe/>
There is a new DLZ based backend, but it uses a different LDAP schema: <http://technik.blogs.nde.ag/2013/01/27/switching-from-dnszone-to-dlz-ldap/>

Comment 1 Stefan Gohmann

2019-01-03 07:23:31 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.