[Pkg-samba-maint] Bug#1006935: samba on bullseye:i386 fails for logging and sockets

[dbn-bugs at sh.werbittewas.de]

Package: samba
Version: 2:4.13.13+dfsg-1~deb11u3
Architecture: i386

we're successfully running samba 2:4.9.5+dfsg-5+deb10u3 in a container
with devuan beowulf (debian buster) since several months, but decides to
migrate all containers to chimaera (bullseye), but this fails for
several reasons.

because the devuan-people doesn't change anything in the
samba-debian-package, they told me to forward the bug towards debian...


1.
having "bind interfaces only = yes" in config, smbd errors out with
"INTERNAL ERROR: open_sockets_smbd()" and "open_sockets_smbd: No sockets
available to bind to"

deactivating this config-entry makes smbd start normally.

2.
having "log file = /var/log/samba/%m.log" in config is completly
ignored. No such files are written, even when setting /varlog/samba to
mode 1777 and having parent dirs all at least at mode 751
(no workaround found)

further tests are stopped for now, because we need the system working,
but it seems, that the performance on network was worse than before
during initial connects.


using the same config with beowulf(buster)-container and samba
2:4.9.5+dfsg-5+deb10u3 works fine. (fortunately we could switch back to
the old container easily). Anything else but the inner system of the
container are equal!

because devuan-people already asked: the "interfaces"-config contains
multiple ip-addresses including 127.0.0.1

the network-config of the container is completed before the container
starts any program (then connecting to it via nsenter)

and as already said: it's really the same as before and now, running the
beowulf(buster)-container...


if there're any additional infos are needed we'll try to give them, any
certain tests with the buggy samba may take a bit time, because we can't
switch the container at every time, but have to wait for evening or
weekend, to really have equal conditions.

regards

d.