[Samba] Broken Dependencies?

[Michael Tokarev]

16.05.2022 15:38, Dirk Laurenz via samba wrote:
> So after trying update, reinstallation, changing to a new sdcard... I get
> the same errors, when starting samba with the backport version:
> 
> 
> [2022/05/16 14:34:36.466993,  0]
> ../../source4/samba/server.c:621(binary_smbd_main)
>    samba version 4.16.1-Debian started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2022
> [2022/05/16 14:34:36.467540,  0]
> ../../lib/util/become_daemon.c:150(daemon_status)
>    daemon_status: daemon 'samba' : Starting process...
> [2022/05/16 14:34:37.208800,  0]
> ../../source4/samba/server.c:897(binary_smbd_main)
>    binary_smbd_main: samba: using 'prefork' process model
> [2022/05/16 14:34:37.319717,  0]
> ../../source4/lib/tls/tlscert.c:67(tls_cert_generate)
>    Attempting to autogenerate TLS self-signed keys for https for hostname
> 'DC03.samba.laurenz.ws'
> [2022/05/16 14:34:37.557399,  0] ../../lib/util/fault.c:172(smb_panic_log)
>    ===============================================================
> [2022/05/16 14:34:37.557734,  0] ../../lib/util/fault.c:173(smb_panic_log)
>    INTERNAL ERROR: Signal 11: Segmentation fault in pid 24413 (4.16.1-Debian)

Lovely. I haven't seen any panics with 4.16 versions so far.
But this is arm, - I never tried samba on arm either.

In debian by default panic action is set to /usr/share/samba/panic-action
which is a script which tries to send email with the backtrace. It is an
old thing, I think it should be changed now to save the backtrace in some
file instead of trying to email it.  There, if there's no "mail" command
installed, the script just exits with exit status 0, and it even if this
command is available, there's a good chance it does not work anyway.

In order to collect a useful backtrace which can be used to diagnose this,
one has to install the dbgsym package for samba (and I guess samba-libs
too), - see https://wiki.debian.org/HowToGetABacktrace for how to add
the necessary line into your apt/sourses.list file, next install
samba-dbgsym and samba-libs-dbgsym packages.  And install gdb package
too.

After that, - it looks like you don't have a working mail command - I'd
suggest you to modify the script, /usr/share/samba/panic-action (or
change "panic action" parameter in smb.conf to point to the new script)
which does just this:

#! /bin/sh
exe=$(readlink /proc/$1/exe)
gdb -x /etc/samba/gdbcommands --batch $exe $1 >/var/log/samba/backtrace.$1 2>&1

(untested but should be close to what's needed).

and post the contents of /var/log/backtrace.NN files here. The
backtrace isn't usually large.

Thanks,

/mjt