On Wed, Dec 23, 2020 at 08:11:25 -0500, Gene Heskett wrote:
> amstatus: bad status on taper SHM-WRITE (dumper): 20 at
> /usr/local/share/perl/5.24.1/Amanda/Status.pm line 929, <$fd>
> line 3411.
[...]
> But that log was overwritten by the flush.sh I did trying to complete
> the backup on vtape-30, so is gone forever. But vtape-31 was not
In Amanda 3.5, the "/var/log/amanda/<CONFIG>/amdump" path is actually
just a symlink pointing to the currently-active amdump file among the multiple
timestamped files (amdump.YYYYMMDDhhmmss), so the original log file should
still be out there.
It will be interesting to compare the contents of the logs from working
and non-working runs. So:
1) what's the timestamp for the run that generated this error?
2) what does
$ grep SHM-WRITE amdump.202012[12]*
show (when run from within the correct .../log/amanda/... directory)?
(The idea being to grep through all the amdump.* files from the past
13 days, just as a quick way to hit both good and bad runs.)
3) is there any correlation between the runs where amstatus returns this
error and other interesting messages appearing in the Amanda Mail
Report for those runs?
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
