> wallace88
>
> If you still plan to try to email your notifications, then test it
> from the command line. In other words, take whatever you have on the
> action field and copy and paste it into your command line.
>
> Also, verify you have the right syntax by typing just "smtpmail" or
> "nsrmail". Both are included with networker, though unsupported, they
> usually work without issues once the syntax is correct.
Well, what I've been using is a filter script I wrote. It captures the
notification stream, looks to see if it contains anything useful (i.e.,
level=full, level=incr, level=5, etc. for our configs) and if so, mailx's
it on. We do this to avoid needless "all skip" reports. I also parse out
things like number of clients, number succeeded, number failed and put
them along with the savegroup name and hostname into the subject line.
Makes for a much more immediately informative email.
In this particular instance, after some reasearch we learned we got no
report due to the savegrp abending. There was an old forgotten ulimit
setting lurking in a shell init file that I've since removed, and I think
it was causing a too-many-open-files issue.
Thanks.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|