Re: amgtar: defaults for NORMAL and STRANGE

2021-01-19 Thread Nathan Stratton Treadway
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.

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.

(You could prevent those messages from ever showing up in the report by
setting them to IGNORE in the config file, but in general I'd say trying
to fix the underlying cause of a STRANGE status is preferable to
suppressing messages completely)


Does that explain the behavor you were seeing?


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


Re: amgtar: defaults for NORMAL and STRANGE

2021-01-19 Thread Tom Robinson
Hi Nathan,

Thanks for your insights and help.

On Tue, 19 Jan 2021 at 17:24, Nathan Stratton Treadway 
wrote:

> On Tue, Jan 19, 2021 at 11:53:52 +1100, Tom Robinson wrote:
> >
> > Also, the man page says there are defaults for NORMAL and STRANGE but
> these
> > 'defaults' don't seem to be included into the application definition
> when I
> > dump the config information with amadmin daily config:
>
> [...]
> > Is the man page incorrect? Are the 'defaults' really applied or do I have
> > to manually specify them in the config file?
>
> I haven't looked closely at this functionality before, but from a quick
> skim of the code in application-src/amgtar.c, it looks like those
> default values are built directly in to the program itself.
>
> That is, they aren't implemented as part of the config system and thus
> don't show in the output of "amadmin ... config", but they do indeed
> exist underneath the hood.
>

Ah, that explains it. Although it is somewhat confusing to not see that in
the config file at first.


> (As a corollary to that, it seems like there isn't any way to completely
> delete the default strings from amgtar's processing, though you can
> override the treatment of a particular regex by explicitly specifying
> it as another type in the config file.)
>
>
> (Are you seeing any situations where it looks like the default strings
> aren't being applied as you would have expected from the man page
> description?)
>
>
CentOS Linux release 8.2.2004 (Core)
amanda 3.5.1

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
  | /usr/bin/tar: ./var/lib/sss/pipes/nss: socket ignored
  | /usr/bin/tar:
./var/lib/sss/pipes/private/sbus-dp_implicit_files.558138: socket ignored
  | /usr/bin/tar: ./var/lib/sss/pipes/private/sbus-dp_implicit_files.782:
socket ignored
  | /usr/bin/tar: ./var/spool/postfix/private/anvil: socket ignored
  | /usr/bin/tar: ./var/spool/postfix/private/bounce: socket ignored
  | /usr/bin/tar: ./var/spool/postfix/private/defer: socket ignored
  | /usr/bin/tar: ./var/spool/postfix/private/discard: socket ignored
  | /usr/bin/tar: ./var/spool/postfix/private/error: socket ignored
  Look in the
'/var/log/amanda/log.error/lambo.motec.com.au._.1.20210120132743.errout'
file for full error messages
  \

More configs:

DLE:
lambo.motec.com.au / {
comp-root-amgtar
}

dumptypes:
define dumptype global {
comment "Global definitions"
auth "bsdtcp"
exclude list optional ".amanda.excludes"
}
define dumptype root-amgtar {
global
program "APPLICATION"
application "app_amgtar"
comment "root partitions dumped with tar"
compress none
index
priority low
}
define dumptype comp-root-amgtar {
root-amgtar
comment "Root partitions with compression dumped with tar"
compress client fast
}
Application:

Note that this config setting:

define application-tool app_amgtar {
comment "amgtar"
plugin  "amgtar"
property "XATTRS" "YES"
property "ACLS" "YES"
#property "GNUTAR-PATH" "/path/to/gtar"
#property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
property"NORMAL" ": socket ignored$"
property append "NORMAL" ": file changed as we read it$"
property append "NORMAL" ": directory is on a different filesystem; not
dumped$"
}

AND this config setting:

define application-tool app_amgtar {
comment "amgtar"
plugin  "amgtar"
property "XATTRS" "YES"
property "ACLS" "YES"
#property "GNUTAR-PATH" "/path/to/gtar"
#property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
#property"NORMAL" ": socket ignored$"
#property append "NORMAL" ": file changed as we read it$"
#property append "NORMAL" ": directory is on a different filesystem;
not dumped$"
}

give the same results in the report.

Kind regards,
Tom


Re: amgtar: Operation not permitted

2021-01-19 Thread Tom Robinson
On Tue, 19 Jan 2021 at 18:39, Diego Zuccato  wrote:

> Il 19/01/21 01:53, Tom Robinson ha scritto:
>
> > I now get a lot of permission warnings and errors. Of particular concern
> > are the 'Operation not permitted' messages:
> Maybe you're running SELinux on the clients and amgtar is not allowed to
> access everything?
>

Diego you are right and thanks for the reminder! I should have checked that
but forgot! There is indeed an SE Alert regarding the access issue.

There is no installed policy for amgtar so I've created one and done a
manual dump which looks good.

Thanks for your insight and help.

Kind regards,
Tom


Re: Wiki down

2021-01-19 Thread Gene Heskett
On Tuesday 19 January 2021 05:37:30 Stefan G. Weichinger wrote:

> The Amanda wiki from zmanda is down
>
> https://wiki.zmanda.com/index.php
>
> Very likely only a hiccup at cloudflare.
>
> But I hope somebody has backups of that (outdated but valid) stuff.

Back up at just after 8AM EST

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 


Re: Wiki down

2021-01-19 Thread Stefan G. Weichinger

Am 19.01.21 um 11:52 schrieb Jeet Bahadur Gurung:

Site is up now.

Regards,
Jeet Bahadur Gurung | Senior Cloud Engineer|BETSOL|


great, thanks


RE: Wiki down

2021-01-19 Thread Jeet Bahadur Gurung
Site is up now.

Regards,
Jeet Bahadur Gurung | Senior Cloud Engineer|BETSOL|

-Original Message-
From: owner-amanda-us...@amanda.org  On Behalf 
Of Stefan G. Weichinger
Sent: 19 January 2021 16:08
To: AMANDA users 
Subject: Wiki down

WARNING: This email originated from outside of BETSOL. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.


The Amanda wiki from zmanda is down

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.zmanda.com%2Findex.phpdata=04%7C01%7Cjeet.gurung%40betsol.com%7Cc9e2fe9e421741d7ac7908d8bc669e3f%7Cb0fb22a6306043889a97cdfc342994d8%7C0%7C0%7C637466496558214592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000sdata=rv1eK48%2BZS3q66c1LMsCccm%2BzKq%2BiN86SC22OikUmU4%3Dreserved=0

Very likely only a hiccup at cloudflare.

But I hope somebody has backups of that (outdated but valid) stuff.
Confidentiality Notice | The information transmitted by this email is intended 
only for the person or entity to which it is addressed. This email may contain 
proprietary, business-confidential and/or privileged material. If you are not 
the intended recipient of this message, be aware that any use, review, 
re-transmission, distribution, reproduction or any action taken in reliance 
upon this message is strictly prohibited. If you received this in error, please 
contact the sender and delete the material from all computers.



Wiki down

2021-01-19 Thread Stefan G. Weichinger



The Amanda wiki from zmanda is down

https://wiki.zmanda.com/index.php

Very likely only a hiccup at cloudflare.

But I hope somebody has backups of that (outdated but valid) stuff.