Seit längerem habe ich ein LB3 unter Proxmox am Laufen. Seit ca. 2 Wochen erhalte ich nun im Minutentakt folgende Samba-Fehlermeldungen per Mail:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 24896 (/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-dbgsym 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.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fc08bbad2d7 in __GI___waitpid (pid=24897, stat_loc=stat_loc@entry=0x7ffd1d817cd8, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#0 0x00007fc08bbad2d7 in __GI___waitpid (pid=24897, stat_loc=stat_loc@entry=0x7ffd1d817cd8, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 0x00007fc08bb2b70f in do_system (line=<optimized out>) at ../sysdeps/posix/system.c:149
#2 0x00007fc08c434231 in smb_panic_s3 () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#3 0x00007fc08c8149df in smb_panic () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0
#4 0x00007fc08c518021 in cups_cache_reload () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#5 0x00007fc08c514b4e in pcap_cache_reload () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#6 0x00007fc08c59d42c in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#7 0x00007fc08c44f26b in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
#8 0x00007fc08bcb2c55 in tevent_common_invoke_timer_handler () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#9 0x00007fc08bcb2dea in tevent_common_loop_timer_delay () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#10 0x00007fc08bcb4139 in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#11 0x00007fc08bcb22d7 in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#12 0x00007fc08bcad7e4 in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#13 0x00007fc08bcada2b in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#14 0x00007fc08bcb2277 in ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
#15 0x00007fc08c59d9fe in start_background_queue () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#16 0x00007fc08c59dd2b in printing_subsystem_init () from /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
#17 0x000055e80e0d704c in main ()
A debugging session is active.
Inferior 1 [process 24896] will be detached.
Quit anyway? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 24896) detached]
/etc/cron.hourly/fake-hwclock:
/sbin/fake-hwclock: 37: /sbin/fake-hwclock: cannot create /etc/fake-hwclock.data: Read-only file system
run-parts: /etc/cron.hourly/fake-hwclock exited with return code 2
/etc/cron.hourly/logrotate:
error: error creating output file /var/lib/logrotate/status.tmp: Read-only file system
run-parts: /etc/cron.hourly/logrotate exited with return code 1
Meine Standar-Linux-Kenntnisse sind hier stark am Limit, bisherige Recherche hat nicht wirklich etwas brauchbares hervorgebracht. An einigen Stellen habe ich gefunden, dass der Fehler durch falsche Plattform-Pakete (ARM, X86, AMD64) versursaht werden kann. Wüsste ich beim LB aber grad nicht, wie das zustandekommen könnte.
hat hierzu jemand eine Idee und kann mir weiterhelfen?
Besten Dank und liebe Grüsse
Kommentar