Re: Amanda 3.5.1 - "ERROR: amcheck-device terminated with signal 11"

On Wed, Oct 14, 2020 at 12:20:33 -0400, Chris Hoogendyk wrote:
> Both lexical.pm and ScanInventory.pm restored to original. New fix
> only patch applied to ScanInventory.pm. amanda.conf restored to use
> oldest.
> 
>    amanda@marlin:~/daily$ amcheck daily
> 
>        Amanda Tape Server Host Check
>        -----------------------------
>        NOTE: Holding disk '/amanda3': 139784192 KB disk space available, using 34926592 KB
>        NOTE: Holding disk '/amanda4': 170082304 KB disk space available, using 65224704 KB
>        NOTE: Holding disk '/amanda5': 240713728 KB disk space available, using 135856128 KB
>              ***** Authorized Use Only *****
> 
>        snapper
>        slot 25: volume 'Bio-Research-028'
>        Will write to volume 'Bio-Research-028' in slot 25.
>        NOTE: skipping tape-writable test
>        Server check took 50.059 seconds
>        Amanda Backup Client Hosts Check
>        --------------------------------
>        Client check: 4 hosts checked in 6.692 seconds.  0 problems found.
>        (brought to you by Amanda 3.5.1)
> 
>    amanda@marlin:~/daily$
[...]> 
> 
> Launched a flush on that. Then the following seems to set up a tape on the second tape drive.
> 
>    amanda@marlin:~/daily$ amtape daily taper
> 
>        slot 31: volume 'Bio-Research-032'
>        Will write to volume 'Bio-Research-032' in slot 31.
> 
>    amanda@marlin:~/daily$

Okay, sounds like things are back to working "normally" on that server,
right?

So, do you still have a second server which is getting coredumps (at
least with the oldest taperscan)?

Based on the investigation so far, it seems like the crash is caused by
tape-inventory records which have no label text along with some specific
other data field values.

If you post the /usr/local/var/amanda/chg-robot-dev-tape-by-id-scsi*
changer state file that other server, we can double check that such
entries exist over there, too.

(Assume they do, then I guess the question will be whether you want to
apply the same ScanInventory.pm patch there, or if you instead want to
try clearing that/those bad inventory record(s) without changing the
installed code on that box....)

							Nathan

----------------------------------------------------------------------------
Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239