---------- Forwarded message ---------
From: Tom Robinson <tom.robin...@motec.com.au>
Date: Thu, 21 Jan 2021 at 09:13
Subject: Re: amgtar: defaults for NORMAL and STRANGE
To: Nathan Stratton Treadway <natha...@ontko.com>


On Wed, 20 Jan 2021 at 16:09, Nathan Stratton Treadway <natha...@ontko.com>
wrote:

> On Wed, Jan 20, 2021 at 14:22:02 +1100, Tom Robinson wrote:
> > I'm still seeing messages in the report that should have been squashed.
> It
> > also doesn't matter what I have configured as 'NORMAL' for the
> application
> > configuration.
> >
> > STRANGE DUMP DETAILS:
> >   /-- lambo.motec.com.au / lev 1 STRANGE
> >   sendbackup: info BACKUP=APPLICATION
> >   sendbackup: info APPLICATION=amgtar
> >   sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc
> > |/usr/lib64/amanda/application/amgtar restore [./file-to-restore]+
> >   sendbackup: info COMPRESS_SUFFIX=.gz
> >   sendbackup: info end
> >   | /usr/bin/tar: ./dev: directory is on a different filesystem; not
> dumped
> >   | /usr/bin/tar: ./proc: directory is on a different filesystem; not
> dumped
> >   | /usr/bin/tar: ./run: directory is on a different filesystem; not
> dumped
> >   | /usr/bin/tar: ./sys: directory is on a different filesystem; not
> dumped
> >   | /usr/bin/tar: ./mnt/s3backup: directory is on a different
> filesystem; not dumped
> >   | /usr/bin/tar: ./var/lib/nfs/rpc_pipefs: directory is on a different
> filesystem; not dumped
> >   ? /usr/bin/tar: ./mnt/s3backup: Warning: Cannot flistxattr: Operation
> not supported
>
> [...]
> >     property        "NORMAL" ": socket ignored$"
> >     property append "NORMAL" ": file changed as we read it$"
> >     property append "NORMAL" ": directory is on a different filesystem;
>
> Note that the man page explaination of NORMAL includes the sentence
> 'These output are in the "FAILED DUMP DETAILS" section of the email
> report if the dump result is STRANGE'.
>
> In this case, the "Operation not supported" message is considered
> STRANGE... which in turn causes all the NORMAL message lines to be
> included in the report output as well.
>
>
I see. I've been working backwards on this. I was trying to squash the
'NORMAL' messaging to make the STRANGE results more clear! I've fixed the
'Operation not supported' issue and the 'NORMAL' messages have gone, too.
Amanda now produces a clean report.



> So presumably once you resolve all of those error messages for a
> particular DLE, that DLE will no show up with a STRANGE DUMP DETAILS
> section at all, in which case those NORMAL-category messages will no
> longer be included in the report.
>
>
Correct.

Thanks for clarifying Nathan.

Kind regards,
Tom

Reply via email to