Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1006935: samba on bullseye:i386 fails for logging and sockets
39 views
Skip to first unread message
dbn-...@sh.werbittewas.de
Mar 8, 2022, 9:20:03 AM3/8/22
to
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.
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.
dbn-...@sh.werbittewas.de
Apr 3, 2022, 4:40:03 AM4/3/22
to
today tested again, but now with a 64bit-container ... no problem at all
(of course exactly same version, config and environment)
so either the problem may be a compiler-problem or maybe a cut-off value
in code due to bad casting...
unfortunately the code-base is too large for us to go deeper into it,
but it would be nice, if it can be solved, before debian buster with its
working version of i386-samba won't be supported any more
Andrés Maldonado
Apr 22, 2022, 12:30:03 PM4/22/22
to
Hello,
I got the same problem as 1. after an 'apt upgrade', which upgraded
Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to
2:4.13.13+dfsg-1~deb11u3.
I'm on Debian Bullseye, I also use a i386 package and I have 'bind
interfaces only = yes' in my config
After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using
snapshot.debian.org), the problem was fixed.
Here is the backtrace:
[2022/04/22 17:16:17.267120, 0] ../../source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2022/04/22 17:16:17.313995, 0]
../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve
connections
[2022/04/22 17:16:17.315414, 0]
../../source3/smbd/server.c:1244(open_sockets_smbd)
open_sockets_smbd: No sockets available to bind to.
[2022/04/22 17:16:17.315751, 0] ../../lib/util/fault.c:159(smb_panic_log)
===============================================================
[2022/04/22 17:16:17.315779, 0] ../../lib/util/fault.c:160(smb_panic_log)
INTERNAL ERROR: open_sockets_smbd() failed in pid 60894 (4.13.13-Debian)
[2022/04/22 17:16:17.315800, 0] ../../lib/util/fault.c:164(smb_panic_log)
If you are running a recent Samba version, and if you think this
problem is not yet fixed in the latest versions, please consider
reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2022/04/22 17:16:17.315819, 0] ../../lib/util/fault.c:169(smb_panic_log)
===============================================================
[2022/04/22 17:16:17.315836, 0] ../../lib/util/fault.c:170(smb_panic_log)
PANIC (pid 60894): open_sockets_smbd() failed in 4.13.13-Debian
[2022/04/22 17:16:17.316116, 0] ../../lib/util/fault.c:274(log_stack_trace)
BACKTRACE: 9 stack frames:
#0 /lib/i386-linux-gnu/libsamba-util.so.0(log_stack_trace+0x30)
[0xf7b3d140]
#1 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic_log+0x76)
[0xf7b3d296]
#2 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic+0x31) [0xf7b3d431]
#3 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff580)
[0xf7dad580]
#4 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff9d3)
[0xf7dad9d3]
#5 /usr/lib/i386-linux-gnu/samba/libsmbd-shim.so.0(exit_server+0x22)
[0xf782d362]
#6 /usr/sbin/smbd(main+0x176e) [0x565d56be]
#7 /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0x106) [0xf75bde46]
#8 /usr/sbin/smbd(_start+0x31) [0x565d63b1]
[2022/04/22 17:16:17.316220, 0] ../../source3/lib/util.c:838(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 60894]
[2022/04/22 17:16:17.376982, 0] ../../source3/lib/util.c:845(smb_panic_s3)
smb_panic(): action returned status 0
[2022/04/22 17:16:17.377067, 0] ../../source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/log/samba/cores/smbd
Regards,
--
Andrés Maldonado
Code Lutin
I got the same problem as 1. after an 'apt upgrade', which upgraded
Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to
2:4.13.13+dfsg-1~deb11u3.
I'm on Debian Bullseye, I also use a i386 package and I have 'bind
interfaces only = yes' in my config
After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using
snapshot.debian.org), the problem was fixed.
Here is the backtrace:
[2022/04/22 17:16:17.267120, 0] ../../source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2022/04/22 17:16:17.313995, 0]
../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve
connections
[2022/04/22 17:16:17.315414, 0]
../../source3/smbd/server.c:1244(open_sockets_smbd)
open_sockets_smbd: No sockets available to bind to.
[2022/04/22 17:16:17.315751, 0] ../../lib/util/fault.c:159(smb_panic_log)
===============================================================
[2022/04/22 17:16:17.315779, 0] ../../lib/util/fault.c:160(smb_panic_log)
INTERNAL ERROR: open_sockets_smbd() failed in pid 60894 (4.13.13-Debian)
[2022/04/22 17:16:17.315800, 0] ../../lib/util/fault.c:164(smb_panic_log)
If you are running a recent Samba version, and if you think this
problem is not yet fixed in the latest versions, please consider
reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2022/04/22 17:16:17.315819, 0] ../../lib/util/fault.c:169(smb_panic_log)
===============================================================
[2022/04/22 17:16:17.315836, 0] ../../lib/util/fault.c:170(smb_panic_log)
PANIC (pid 60894): open_sockets_smbd() failed in 4.13.13-Debian
[2022/04/22 17:16:17.316116, 0] ../../lib/util/fault.c:274(log_stack_trace)
BACKTRACE: 9 stack frames:
#0 /lib/i386-linux-gnu/libsamba-util.so.0(log_stack_trace+0x30)
[0xf7b3d140]
#1 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic_log+0x76)
[0xf7b3d296]
#2 /lib/i386-linux-gnu/libsamba-util.so.0(smb_panic+0x31) [0xf7b3d431]
#3 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff580)
[0xf7dad580]
#4 /usr/lib/i386-linux-gnu/samba/libsmbd-base.so.0(+0x1ff9d3)
[0xf7dad9d3]
#5 /usr/lib/i386-linux-gnu/samba/libsmbd-shim.so.0(exit_server+0x22)
[0xf782d362]
#6 /usr/sbin/smbd(main+0x176e) [0x565d56be]
#7 /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0x106) [0xf75bde46]
#8 /usr/sbin/smbd(_start+0x31) [0x565d63b1]
[2022/04/22 17:16:17.316220, 0] ../../source3/lib/util.c:838(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 60894]
[2022/04/22 17:16:17.376982, 0] ../../source3/lib/util.c:845(smb_panic_s3)
smb_panic(): action returned status 0
[2022/04/22 17:16:17.377067, 0] ../../source3/lib/dumpcore.c:315(dump_core)
dumping core in /var/log/samba/cores/smbd
Regards,
--
Andrés Maldonado
Code Lutin
Michael Tokarev
Apr 22, 2022, 2:30:07 PM4/22/22
to
Control: tag -1 + confirmed
22.04.2022 19:15, Andrés Maldonado wrote:
> Hello,
>
> I got the same problem as 1. after an 'apt upgrade', which upgraded Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to
> 2:4.13.13+dfsg-1~deb11u3.
>
> I'm on Debian Bullseye, I also use a i386 package and I have 'bind interfaces only = yes' in my config
>
> After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using snapshot.debian.org), the problem was fixed.
Just confirmed this in a local 32bit chroot. smbd immediately crashes at
startup with bind interfaces only = yes.
However I see no changes between 4.13.13+dfsg-1~deb11u2 and 4.13.13+dfsg-1~deb11u3
which might be problematic in this context. Everything in there is completely
unrelated.
Lemme see if to-be 4.13.13+dfsg-1+deb11u4 works...
/mjt
22.04.2022 19:15, Andrés Maldonado wrote:
> Hello,
>
> I got the same problem as 1. after an 'apt upgrade', which upgraded Samba and it's dependencies from 2:4.13.13+dfsg-1~deb11u2 to
> 2:4.13.13+dfsg-1~deb11u3.
>
> I'm on Debian Bullseye, I also use a i386 package and I have 'bind interfaces only = yes' in my config
>
> After downgrading Samba to 2:4.13.13+dfsg-1~deb11u2 (using snapshot.debian.org), the problem was fixed.
startup with bind interfaces only = yes.
However I see no changes between 4.13.13+dfsg-1~deb11u2 and 4.13.13+dfsg-1~deb11u3
which might be problematic in this context. Everything in there is completely
unrelated.
Lemme see if to-be 4.13.13+dfsg-1+deb11u4 works...
/mjt
Michael Tokarev
Apr 22, 2022, 2:40:05 PM4/22/22
to
22.04.2022 21:20, Michael Tokarev wrote:
..
and deb11u4 which can fix this issue, but the prob (with locally
built deb11u4) is gone. The build is performed on a stable
bullseye schroot.
Hmm..
Lemme re-build deb11u3 locally to see if this is maybe a build
issue?..
/mjt
..
> Lemme see if to-be 4.13.13+dfsg-1+deb11u4 works...
And this one works indeed. There's no changes between deb11u3
and deb11u4 which can fix this issue, but the prob (with locally
built deb11u4) is gone. The build is performed on a stable
bullseye schroot.
Hmm..
Lemme re-build deb11u3 locally to see if this is maybe a build
issue?..
/mjt
Michael Tokarev
Apr 22, 2022, 3:50:04 PM4/22/22
to
22.04.2022 21:37, Michael Tokarev wrote:
> Lemme re-build deb11u3 locally to see if this is maybe a build
> issue?..
So I just rebuilt ~deb11u3 in a clean bullseye i386 schroot environment,
> Lemme re-build deb11u3 locally to see if this is maybe a build
> issue?..
the standard way.
With the resulting samba-libs package samba does not crash at startup anymore,
and it all other sympthoms mentioned in this bugreport are gone too.
And the binaries are just too different to understand what's going on there.
Unfortunately there's no easily available build logs of this deb11u3 build,
to see maybe there are some interesting things in there.
*sigh*.
/mjt
0 new messages