ich habe eine VM mit Debian 11 laufen, die sich regelmäßig für's Backup per SMB (mit cifs-utils) mit dem HomeServer (Linux Mint Debian Edition, Samba Version 4.17.12-Debian) verbindet. Es klappt auch alles problemlos, nur bekomme ich anschliessend immer E-Mails mit z. B. diesem Text:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 313418 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 313418.
It may have died unexpectedly, or you may not have permission to debug
the process.
Im Log vom smbd habe ich dazu z. B. so etwas gefunden:
Code: Alles auswählen
[2024/04/02 20:20:02.095219, 0] ../../source3/param/loadparm.c:3461(process_usershare_file)
process_usershare_file: stat of /var/lib/samba/usershares/exchange_pool_borgbackup failed. Keine Berechtigung
[2024/04/02 20:20:03.724399, 0] ../../lib/util/fault.c:173(smb_panic_log)
===============================================================
[2024/04/02 20:20:03.724480, 0] ../../lib/util/fault.c:174(smb_panic_log)
INTERNAL ERROR: Signal 11: Speicherzugriffsfehler in pid 435691 (4.17.12-Debian)
[2024/04/02 20:20:03.724504, 0] ../../lib/util/fault.c:178(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.
[2024/04/02 20:20:03.724525, 0] ../../lib/util/fault.c:183(smb_panic_log)
===============================================================
[2024/04/02 20:20:03.724544, 0] ../../lib/util/fault.c:184(smb_panic_log)
PANIC (pid 435691): Signal 11: Speicherzugriffsfehler in 4.17.12-Debian
[2024/04/02 20:20:03.726041, 0] ../../lib/util/fault.c:292(log_stack_trace)
BACKTRACE: 29 stack frames:
#0 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(log_stack_trace+0x2e) [0x7fcf564f855e]
#1 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(smb_panic+0x9) [0x7fcf564f87b9]
#2 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(+0x1851) [0x7fcf564f8851]
#3 /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7fcf562f1050]
#4 /lib/x86_64-linux-gnu/libc.so.6(+0xa9cb6) [0x7fcf5635ecb6]
#5 /lib/x86_64-linux-gnu/libsmbconf.so.0(volume_label+0x4b) [0x7fcf5681012b]
#6 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_do_qfsinfo+0xa1) [0x7fcf56905481]
#7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_smb2_request_process_getinfo+0x23c) [0x7fcf5696353c]
#8 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_smb2_request_dispatch+0x140c) [0x7fcf5694b8bc]
#9 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_smb2_request_dispatch_immediate+0x4c) [0x7fcf5694cb8c]
#10 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_invoke_immediate_handler+0x17a) [0x7fcf5649ee2a]
#11 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0x16) [0x7fcf5649ee46]
#12 /lib/x86_64-linux-gnu/libtevent.so.0(+0xebfb) [0x7fcf564a4bfb]
#13 /lib/x86_64-linux-gnu/libtevent.so.0(+0xcef7) [0x7fcf564a2ef7]
#14 /lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x91) [0x7fcf5649dba1]
#15 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fcf5649de7b]
#16 /lib/x86_64-linux-gnu/libtevent.so.0(+0xce97) [0x7fcf564a2e97]
#17 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base-samba4.so.0(smbd_process+0x82f) [0x7fcf5693a21f]
#18 /usr/sbin/smbd(+0x9e00) [0x55db65a18e00]
#19 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x7fcf5649e8c1]
#20 /lib/x86_64-linux-gnu/libtevent.so.0(+0xee07) [0x7fcf564a4e07]
#21 /lib/x86_64-linux-gnu/libtevent.so.0(+0xcef7) [0x7fcf564a2ef7]
#22 /lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x91) [0x7fcf5649dba1]
#23 /lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fcf5649de7b]
#24 /lib/x86_64-linux-gnu/libtevent.so.0(+0xce97) [0x7fcf564a2e97]
#25 /usr/sbin/smbd(main+0x1489) [0x55db65a16269]
#26 /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7fcf562dc24a]
#27 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fcf562dc305]
#28 /usr/sbin/smbd(_start+0x21) [0x55db65a16b41]
[2024/04/02 20:20:03.726458, 0] ../../source3/lib/util.c:702(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 435691]
[2024/04/02 20:20:03.870293, 0] ../../source3/lib/util.c:709(smb_panic_s3)
smb_panic(): action returned status 0
[2024/04/02 20:20:03.870440, 0] ../../source3/lib/dumpcore.c:317(dump_core)
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
Daher die Frage, ob bei der Parametrisierung der Freigabe(n) noch etwas fehlt oder ob ich das besser direkt über Samba erledige. Es sind nur wenige Freigaben und die müssen ja nicht dauernd geändert werden.
Danke für die Hilfe,
Achim
