FS#40455 - [samba] 4.1.7: dlz_bind9_9.so: incorrect driver API version 2, requires 3

Attached to Project: Arch Linux
Opened by DJ Lucas (DJ_Lucas) - Monday, 19 May 2014, 19:44 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 15 December 2014, 10:12 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: After update to Bind-9.10.x, bind9_dlz fails with error about API version.

Additional info: Specific error is:
dlz_dlopen: /usr/lib/samba/bind9/dlz_bind9_9.so: incorrect driver API version 2, requires 3

Steps to reproduce:
Setup Samba4 Active Directory Domain Controller using bind9 for DNS backend and restart named service.

I'm not sure how to handle this within packaging. I presume it will be addressed in Samba 4.1.8 (it has yet to be addressed in samba git), but that is not scheduled for release until June 3rd. I suppose in the mean time, samba4 AD DC users must downgrade to Bind 9.9 or patch it in. It looks to be a fairly simple patch, but I haven't tested yet. If tesing seems to work, I'll post patch here, but it should not be applied in Arch. Also, probably bind<=9.9 should be added to optdepends for at least the "samba" package anyway. I'll be pinging samba devs about this as well.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 15 December 2014, 10:12 GMT
Reason for closing:  Fixed
Comment by DJ Lucas (DJ_Lucas) - Monday, 19 May 2014, 19:57 GMT
Unfortunately, fix is not as easy as I had hoped. Upstream notified here: https://bugzilla.samba.org/show_bug.cgi?id=10620
Comment by Darth Vader (DVader) - Wednesday, 09 July 2014, 08:28 GMT
Hello,

Any news about this bug when it will be fixed ?
Comment by DJ Lucas (DJ_Lucas) - Saturday, 22 November 2014, 07:33 GMT
Patch is available at https://attachments.samba.org/attachment.cgi?id=10447&action=diff&collapsed=&context=patch&format=raw&headers=1 but 3.1.14 should be here soon enough.
Comment by DJ Lucas (DJ_Lucas) - Monday, 15 December 2014, 08:12 GMT
Bug can now be closed (fixed upstream).

Loading...