Bug 15643 - Samba 4.20.0 DLZ module crashes BIND on startup
Summary: Samba 4.20.0 DLZ module crashes BIND on startup
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.20.0
Hardware: x64 Linux
: P5 regression (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2024-05-08 14:58 UTC by Rob Foehl
Modified: 2024-05-08 22:26 UTC (History)
1 user (show)

See Also:

GDB-captured backtrace of failed named startup (6.25 KB, text/plain)
2024-05-08 14:58 UTC, Rob Foehl
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Foehl 2024-05-08 14:58:28 UTC
Created attachment 18300 [details]
GDB-captured backtrace of failed named startup

Samba AD DC using DLZ DNS on Fedora 39 with current Samba 4.19.6 / BIND 9.18.24 packages upgraded to Fedora 40, Samba 4.20.0 / BIND 9.18.26.  named consistently crashes on startup when trying to load the Samba-provided DLZ module; stack trace attached.  No other indications of issues, including samba-tool dbcheck.  Samba itself seems to operate fine otherwise, including answering domain-related queries via LDAP.
Comment 1 Rob Foehl 2024-05-08 15:07:52 UTC
Cloned from previous report for Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2278016

Component and severity are a bit of a guess -- it's crashing deep in the LDB code, the DLZ plugin doesn't appear to have been modified at all recently, and the particular sam.ldb it's failing to load hasn't been touched since it was written out during DC provisioning on a Fedora 37 install about 18 months ago, likely by 4.17.4.