Sorry to keep replying to myself, but after 300MB of debuginfo, here's a
more complete backtrace:
Core was generated by `/usr/bin/perl /usr/lib64/amanda/amcheck-device math
math'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
106
To verify everything, I swapped back in a regular tape, no problem. I
put the cleaning tape back in and the problem returns.
Checking coredumpctl (this is a Fedora system, so systemd is handling
the cores) I see that... perl itself is segfaulting. Looking at the
backtrace (which is
Most often, my laptop backup get started from the
client using ambackup. However, if it happens to
be booted when the amanda server does its dumps,
the laptop gets backed up then also.
Last night I ran ambackup from the laptop but it
had not finished by bedtime so I left it on to
complete and
I replaced the last tape in my 48-slot library with a cleaning tape
since I'd rather not bother with manually cleaning the drive. But this
appears to make amcheck segfault:
AMANDA:backup2:amanda/server/math> amcheck -s math
Amanda Tape Server Host Check
-
NOTE:
