On Mon, Jan 06, 2020 at 16:13:25 -0500, Chris Hoogendyk wrote:
> Well, this situation came up again, and that didn't actually work.
Am I correct in understanding that
* by "that" you mean "updating the 'log' symlink to point to the old
log file", and
* by "didn't actually work" you mean that the report email was empty?
> I tried switching the log symlink to point to the Saturday night log
> file and then running amcheck. That didn't work. So, I tried also
> changing the amdump symlink to the Saturday night amdump file. The
> two together gave me the output for the Saturday night run. It
(I am guessing you mean "amstatus" [not "amcheck"] here?)
As far as I understand, "amcleanup" looks only at the log file, while
amstatus uses only the "amdump" (or "amflush") file, so it would make
sense that you'd need to update that symlink to get amstatus to work...
though you could instead just use the "--file" option to specify the
explicit file name for the older run.
> showed that the tape was full; and, with the holding disks also
> full, 5 DLEs were waiting for dumping, one had failed, and Amanda
> was simply hung waiting.
(yeah, this "simply hung waiting" situation is the real issue, but to
figure that out you'll need to look at the process debug files for
underlying processes)
> Assuming that the symlinks were doing the
> job, I issued an `amcleanup -k daily`. That seemed to work. The
> processes were killed and a report was sent. However, the report was
> virtually empty. So something else is missing in terms of symlinks
> or coding or something.
I looked again but don't immediately see "amreport" using anything other
than the same log file symlink that "amcleanup" uses.
What happens if you use "amreport -l <filename> --from-amdump" pointing
directly to the log file from the Saturday run? Is it possible that the
log file is simply truncated somehow?
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
