Open addohm opened 1 year ago
Here's a response from the samba devs.
this is not a Samba bug but a problem of your compiled binaries. Also 4.12.x is quite old and no longer supported, but this is not the problem. You might want to consult one of the comapnies offerering commercial samba support, see the samba.org web site for support options.
On 22.07.23 05:41, Adam Leven wrote:
This is a newly created docker container using docker compose. The server just crashes and restrarts constantly with: Error loading shared library libpopt.so.0: Exec format error (needed by /usr/bin/smbclient) Error loading shared library libpopt.so.0: Exec format error (needed by /usr/lib/samba/libpopt-samba3-cmdline-samba4.so) Error loading shared library libpopt.so.0: Exec format error (needed by /usr/lib/samba/libpopt-samba3-samba4.so) Error relocating /usr/lib/samba/libpopt-samba3-cmdline-samba4.so: poptGetInvocationName: symbol not found Error relocating /usr/lib/samba/libpopt-samba3-samba4.so: poptGetInvocationName: symbol not found Error relocating /usr/bin/smbclient: poptSetOtherOptionHelp: symbol not found Error relocating /usr/bin/smbclient: poptFreeContext: symbol not found Error relocating /usr/bin/smbclient: poptGetArg: symbol not found Error relocating /usr/bin/smbclient: poptPrintUsage: symbol not found Error relocating /usr/bin/smbclient: poptPeekArg: symbol not found Error relocating /usr/bin/smbclient: poptGetOptArg: symbol not found Error relocating /usr/bin/smbclient: poptGetContext: symbol not found Error relocating /usr/bin/smbclient: poptGetNextOpt: symbol not found Error relocating /usr/bin/smbclient: poptHelpOptions: symbol not found
===============================================================
INTERNAL ERROR: Signal 11 in pid 413 (4.12.2)
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
===============================================================
PANIC (pid 413): internal error
unable to produce a stack trace on this platform
dumping core in /var/log/samba/cores/smbd
===============================================================
INTERNAL ERROR: Signal 11 in pid 414 (4.12.2)
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
===============================================================
PANIC (pid 414): internal error
unable to produce a stack trace on this platform
dumping core in /var/log/samba/cores/smbd
===============================================================
INTERNAL ERROR: Signal 11 in pid 415 (4.12.2)
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
===============================================================
PANIC (pid 415): internal error
unable to produce a stack trace on this platform
dumping core in /var/log/samba/cores/smbd
So if that's the case, there's probably some sys req that needs to be disclosed before using this docker container.
I've recently had to commission a new NAS and am running into an issue with the following error:
The logs are inundated with with this and only this. The only things I can find anywhere near this error are a decade old or gentoo specific. The only thing I can think of is that its running debian 12. I didn't have this issue on a previously commissioned server running ubuntu server running jammy jellyfish.
uname -a
Linux levenas 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 (2023-07-03) x86_64 GNU/Linux
lsb_release
cat /etc/os-release
docker compose file