Just to follow up on this. I haven't had this happen too often, so it hasn't come up since Nathan's
suggestion in this message – until this weekend. My run from Monday evening returned early with a
status indicating that there was no tape drive available and no holding space left. This is on a
system with two LTO7 tape drives. So, seems like I had some things hung up.
$ amstatus daily
only gives me the latest run, for which I already have the email report. `ps -ef | grep amanda`
shows that I have two amanda runs active. The dumper0 through 9 processes show the log filename; so,
I can sort the two runs based on that, and then the process IDs and parent process IDs point me back
to the instance of the driver that spawned the other processes.
In my case, /usr/local/etc/amanda/daily/log/... is where I looked to find the appropriate amdump or
amflush files based on the date matching what I see in the `ps -ef`. Then,
$ amstatus --file=amdump.20191103233003 daily
gave me the report I wanted for that run. After I saw that it was indeed hung, a simple kill of the
driver process for that instance of amanda terminated everything associated with that run and
resulted in the appropriate email report being sent.
Back to a clean slate now.
Thank you Nathan!
(Oh, and sorry about the blank email earlier. I clicked on the window to bring it to the front and
accidentally clicked on the send.)
On 9/5/19 5:25 PM, Nathan Stratton Treadway wrote:
On Thu, Sep 05, 2019 at 14:12:29 -0400, Chris Hoogendyk wrote:
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?
[...]
As a followup question, How do I get amstatus to tell me about
multiple parallel runs and then deal with those individually?
Short answer: use the --file option on "amstatus", after looking in
/var/log/amanda/<CONFIG> (or whatever your "logdir" is pointed to) to
find the specific amdump.<DATETIME> (or amflush.*) file you want to look
at.
I don't have a lot of experience with parallel runs, but off hand I
don't believe there is a way to get amstatus to do "show me the amdump
sessions that are currently running" -- you have to figure that out some
other way, or run amstatus on each file and look through the output to
see which ones are still underway (e.g. the "taped" DLE counts are less
than the total number of DLEs or whatever).
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
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geosciences Departments
(*) \(*) -- 315 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
