samba - Dec 2023 - bind crashes after samba upgrade

Finally biting the bullet and upgrading some old Samba servers.
This particular server is running 4.10.16 and as a first step I'm
attempting to upgrade it to 4.12.15 (I think I remember something
about 4.11.x not handling the upgrade properly).

Samba seems to run OK but bind9 will crash when loading the dns with dlopen:
=================named[25566]: sizing zone task pool based on 0 zones
named[25566]: Loading 'AD DNS Zone' using driver dlopen
bind9.service: Main process exited, code=killed, status=11/SEGV
kwsrvr01 rndc[25581]: rndc: connect failed: 127.0.0.1#953: connection refused
systemd[1]: bind9.service: Control process exited, code=exited status=1
systemd[1]: bind9.service: Unit entered failed state
systemd[1]: bind9.service: Failed with result 'signal'.
=================Bind will start fine if I disable referencing Samba's
named.conf file
(and I am using the proper version), but of course it's practically
useless without the database.

Any assistance is appreciated.
Thank you,
Chris

On Sun, 24 Dec 2023 17:05:21 -0500
Sonic via samba <samba at lists.samba.org> wrote:
> Finally biting the bullet and upgrading some old Samba servers.
> This particular server is running 4.10.16 and as a first step I'm
> attempting to upgrade it to 4.12.15 (I think I remember something
> about 4.11.x not handling the upgrade properly).
> 
> Samba seems to run OK but bind9 will crash when loading the dns with
> dlopen: =================> named[25566]: sizing zone task pool based on
0 zones
> named[25566]: Loading 'AD DNS Zone' using driver dlopen
> bind9.service: Main process exited, code=killed, status=11/SEGV
> kwsrvr01 rndc[25581]: rndc: connect failed: 127.0.0.1#953: connection
> refused systemd[1]: bind9.service: Control process exited,
> code=exited status=1 systemd[1]: bind9.service: Unit entered failed
> state systemd[1]: bind9.service: Failed with result 'signal'.
> =================> Bind will start fine if I disable referencing
Samba's named.conf file
> (and I am using the proper version), but of course it's practically
> useless without the database.
> 
> Any assistance is appreciated.
> Thank you,
> Chris
> 
First, Merry Christmas :-)

Lets try to help you with your problem (in between cooking the
Christmas dinner ).

I think the place to start is with your named.conf file.

Rowland

25.12.2023 01:05, Sonic via samba :
> Finally biting the bullet and upgrading some old Samba servers.
> This particular server is running 4.10.16 and as a first step I'm
> attempting to upgrade it to 4.12.15 (I think I remember something
> about 4.11.x not handling the upgrade properly).
This is most likely due to a bug in samba which is fixed in samba 4.18.0,
fcecdfa8e5c651d4a27f8fcd5df6e9bce37ed8a7 s4:dnsserver: Rename dns_name_equal()
to samba_dns_name_equal()

Maybe you can upgrade directly to some current version..

/mjt

On 24.12.2023 23:05, Sonic via samba wrote:
> Finally biting the bullet and upgrading some old Samba servers.
> This particular server is running 4.10.16 and as a first step I'm
> attempting to upgrade it to 4.12.15 (I think I remember something
> about 4.11.x not handling the upgrade properly).
>
> Samba seems to run OK but bind9 will crash when loading the dns with
dlopen:
> =================> named[25566]: sizing zone task pool based on 0 zones
> named[25566]: Loading 'AD DNS Zone' using driver dlopen
> bind9.service: Main process exited, code=killed, status=11/SEGV
> kwsrvr01 rndc[25581]: rndc: connect failed: 127.0.0.1#953: connection
refused
> systemd[1]: bind9.service: Control process exited, code=exited status=1
> systemd[1]: bind9.service: Unit entered failed state
> systemd[1]: bind9.service: Failed with result 'signal'.
> =================> Bind will start fine if I disable referencing
Samba's named.conf file
> (and I am using the proper version), but of course it's practically
> useless without the database.
>
> Any assistance is appreciated.
> Thank you,
> Chris
>
Hi Chris,

Couldn't you setup a completely new Debian VM with the latest Samba from 
backports, sync with the old one, transfer the FSMO roles, and then 
demote the old one?

Updating an old DC always seems to be a serious PITA.

Best regards and Merry Christmas,

Peter