Since Samba update yesterday I get emails with:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 7388 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 7388.
It may have died unexpectedly, or you may not have permission to debug
the process.I found a similar topic in this forum, but no solution. Maybe a bug?
Drives + RAM are good.
I'm seeing the same.
Hi,
I get the same messages with a new installation of OMV 3 after running OMV 2 on this machine for quite a while.
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 30035 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.
If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Debian. For information about the procedure for submitting bug reports,
please see http://www.debian.org/Bugs/Reporting or the reportbug(1)
manual page.
[New LWP 30036]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fd0ce261b89 in waitpid () from /lib/x86_64-linux-gnu/libc.so.6
#0 0x00007fd0ce261b89 in waitpid () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007fd0ce1e912b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007fd0cfb360c1 in smb_panic_s3 () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#3 0x00007fd0d17efe5f in smb_panic () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
#4 0x00007fd0d17f007f in ?? () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
#5 <signal handler called>
#6 0x00007fd0d13de5a1 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#7 0x00007fd0ce76d650 in ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
#8 0x00007fd0ce76d273 in ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
#9 0x00007fd0ce76639b in _talloc_free () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
#10 0x00007fd0d13f1693 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#11 0x00007fd0d13f1b3e in smbd_exit_server_cleanly () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#12 0x00007fd0cf4dbcc2 in exit_server_cleanly () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-shim.so.0
#13 0x00007fd0d13d2620 in smbd_server_connection_terminate_ex () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#14 0x00007fd0d13d5849 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#15 0x00007fd0cfb563a1 in run_events_poll () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#16 0x00007fd0cfb56617 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#17 0x00007fd0ce55743d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#18 0x00007fd0ce5575db in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#19 0x00007fd0d13c4088 in smbd_process () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#20 0x0000558458634dd0 in ?? ()
#21 0x00007fd0cfb563a1 in run_events_poll () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#22 0x00007fd0cfb56617 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#23 0x00007fd0ce55743d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#24 0x00007fd0ce5575db in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#25 0x00005584586315e5 in main ()
A debugging session is active.
Inferior 1 [process 30035] will be detached.
Quit anyway? (y or n) [answered Y; input not from terminal]
.Any idea?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!