samba - Dec 2023 - bind crashes after samba upgrade

On Wed, 27 Dec 2023 12:09:50 -0500
Sonic via samba <samba at lists.samba.org> wrote:
> On Wed, Dec 27, 2023 at 11:52?AM Rowland Penny via samba
> <samba at lists.samba.org> wrote:
> > What are the full log messages when named starts and then crashes ?
> I just have what is in the journal:
> Instead of:
> ================================> named[266]: Loading 'AD DNS
Zone' using driver dlopen
> named[266]: samba_dlz: started for DN DC=my,DC=example,DC=com
> named[266]: samba_dlz: starting configure
> ================================> I get:
> ================================> named[2785]: Loading 'AD DNS
Zone' using driver dlopen
> systemd[1]: bind9.service: Main process exited, code=killed,
> status=11/SEGV ================================> 
One of the first things I do after installing bookworm is to install
rsyslog and turn off the journal, I get in /var/log/syslog:

2023-12-25T11:02:14.540910+00:00 tmpdc1 systemd[1]: Starting named.service -
BIND Domain Name Server...
2023-12-25T11:02:14.596133+00:00 tmpdc1 named[4911]: starting BIND
9.18.19-1~deb12u1-Debian (Extended Support Version) <id:>
2023-12-25T11:02:14.596328+00:00 tmpdc1 named[4911]: running on Linux aarch64
6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24)
2023-12-25T11:02:14.596413+00:00 tmpdc1 named[4911]: built with 
'--build=aarch64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${pre>
2023-12-25T11:02:14.596696+00:00 tmpdc1 named[4911]: running as: named -f -u
bind
2023-12-25T11:02:14.596783+00:00 tmpdc1 named[4911]: compiled by GCC 12.2.0
2023-12-25T11:02:14.596856+00:00 tmpdc1 named[4911]: compiled with OpenSSL
version: OpenSSL 3.0.10 1 Aug 2023
2023-12-25T11:02:14.596936+00:00 tmpdc1 named[4911]: linked to OpenSSL version:
OpenSSL 3.0.11 19 Sep 2023
2023-12-25T11:02:14.597018+00:00 tmpdc1 named[4911]: compiled with libuv
version: 1.44.2
2023-12-25T11:02:14.597086+00:00 tmpdc1 named[4911]: linked to libuv version:
1.44.2
2023-12-25T11:02:14.597163+00:00 tmpdc1 named[4911]: compiled with libxml2
version: 2.9.14
2023-12-25T11:02:14.597232+00:00 tmpdc1 named[4911]: linked to libxml2 version:
20914
[really big snip]

It just goes on and on.
> I could try and enable some logging for next time.
Would you the instructions on how to install rsyslog ?
> I'm thinking it may be better to get 4.10 upgraded to 4.11 since the
> database changes before attempting the jump to 4.18.
Possibly.

Rowland

>         /* forwarders {
>                 172.26.62.1;
>         };
Is there a reason why this is half-commented out?
> named.conf.local
> ====================> include
"/usr/local/samba/private/named.conf";
> ====================
Is the correct BIND_DLZ module enabled in the above file?

Kris Lou
klou at themusiclink.net

On Wed, Dec 27, 2023 at 12:25?PM Rowland Penny via samba
<samba at lists.samba.org> wrote:
> One of the first things I do after installing bookworm is to install
> rsyslog and turn off the journal, I get in /var/log/syslog:
> Would you the instructions on how to install rsyslog ?
I've just set up a logging section in bind and I can adjust the
severity level when attempting this next time. I have it saving to
flat files.

27.12.2023 20:24, Rowland Penny via samba:
...
> One of the first things I do after installing bookworm is to install
> rsyslog and turn off the journal, I get in /var/log/syslog:
Curious, how do you turn off the journal?  Do you mean
just saving to /var/log/journal/, or /dev/log redirection?
And another curiocity, what for? :)

/mjt

On Wed, Dec 27, 2023 at 12:25?PM Rowland Penny via samba
<samba at lists.samba.org> wrote:
<>

I attacked this in another way. Decided to take bind out of the
equation if possible and changed the dns backend of the running 4.10
to the samba internal one. No issues there and I didn't really need
the complexity of bind anyway. DNS and user auth worked just fine.
I then tried the in-place upgrade and same issue - DNS worked fine but
no users could authenticate.

So it looks like trying to make the jump by doing a DC join to the
latest bookworm-backport is on the agenda.

Would like to clarify a few items that will hopefully smooth the way:
When the wiki states "Create a hot-backup of the
/usr/local/samba/private/idmap.ldb file on the existing DC" does that
mean do the backup while Samba is running?
And what about the restore on the new DC? Is that a hot-restore, or
should Samba be shut down?
And in regards to the Sysvol sync - is that done with the command
shown - "samba-tool ntacl sysvolreset" or do I need to manually copy
the sysvol folder from the old DC to the new one first (or after)? If
manual copy, what's the recommended procedure?

Thank you,
Chris