Amanda 3.5.1 on Ubuntu LTS Server 16.04 with LTO7 tape library with 2 drives.
It has not been uncommon that my Amanda runs go over 24 hours. Thus a second Amanda starts up and
they run in parallel until the first is completed. No problem. I've got two tape drives.
Today I got an Amanda report that no tape drives were available last night and the holding disk
space was full, so most of the backup aborted. Bummer. Went in an saw a gob of Amanda processes
running. Although my email said that the report was from the September 4th run, amstatus said it was
giving me information about the September 4th run. What about the others?
From various pieces of information, I decided there were two runs from August 31 and Septermber 1st
that were hung and their tapers were holding the drives. amcleanup -k said:
amcleanup: no unprocessed logfile to clean up
amcleanup: /usr/local/sbin/amcleanupdisk stderr: amcleanupdisk: Can't kill a
non-numeric process
ID at /usr/local/share/perl/5.22.1/Amanda/Holding.pm line 244.
amcleanup: /usr/local/sbin/amcleanupdisk stderr:
So, I killed key processes until they all disappeared. No email reports happened from that, although
I remember getting reports in the past after killing a hung Amanda. After that, I did an amcheck,
which came up clean, and then an amflush, which gave me the same error as the amcleanup:
amanda@marlin:~$ amcheck daily
Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk '/amanda3': only 65011712 KB free, using nothing
WARNING: Not enough free space specified in amanda.conf
WARNING: holding disk '/amanda4': only 0 KB free, using nothing
WARNING: Not enough free space specified in amanda.conf
***** Authorized Use Only *****
snapper
slot 9: volume 'Bio-Research-009'
Will write to volume 'Bio-Research-009' in slot 9.
NOTE: skipping tape-writable test
slot 2: volume 'Bio-Daily-003'
Will write to volume 'Bio-Daily-003' in slot 2.
NOTE: skipping tape-writable test
Server check took 52.750 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 4 hosts checked in 4.757 seconds. 0 problems found.
(brought to you by Amanda 3.5.1)
amanda@marlin:~$ amflush daily
amflush: Can't kill a non-numeric process ID at
/usr/local/share/perl/5.22.1/Amanda/Holding.pm
line 244.
How do I straighten this out so that Amanda resumes proper runs tonight?
As a followup question, How do I get amstatus to tell me about multiple parallel runs and then deal
with those individually?
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
