On Tue, Aug 27, 2019 at 15:15:57 -0400, Chris Hoogendyk wrote:
> When I upgraded one of my servers to Amanda 3.5.1, I had to run
> amdump from a script (out of cron), because . . .
>
> Now it doesn't send out an email report when it is finished.
Did you switch to using the script at the same time you upgraded to
3.5.1? That is, did you ever have working reports on this server, either
pre-3.5.1 called from your script, or 3.5.1 called directly from cron?
(Obviously calling it from a script should work; I have a 3.5.1 system
running on Ubuntu which sends email reports from a script-invoked amdump
just fine.)
> What is my workaround? I've looked through the amdump and amanda man
(What OS is running on this system, and what was the origin of your
Amanda binaries?)
What do you get when you run the following commands?
$ amgetconf <CONFIG> mailto
$ amgetconf <CONFIG> send-amreport-on
$ amgetconf <CONFIG> mailer
Does the executable shown in the "mailer" parameter actually exist?
> pages. I don't see an option to tell it, "please DO send an email
> report." I also did check all the various places that might hint at
> an email getting hung up, but didn't find any evidence in any of the
> logs or spool directories that any had ever been sent.
Do you have any "amreport.*.debug" files in your
<path-to-amanda-logs>/server/<CONFIG>/ directory?
If so, look in those log files for a line containing the string "invoking mail
app:", and see if anything interestinng shows up between that line and
onne saying "waiting for child process to finish.." (which normally is
the next line in the log, I think)
If those amreport debug files don't exist, look in the amdump.*.debug
files for lines with the string "amreport" to see if it's trying
and failing to run amreport, or completely skipping that step.
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - natha...@ontko.com - 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
