Fwd: amgtar: defaults for NORMAL and STRANGE

-- Forwarded message - From: Tom Robinson Date: Thu, 21 Jan 2021 at 09:13 Subject: Re: amgtar: defaults for NORMAL and STRANGE To: Nathan Stratton Treadway On Wed, 20 Jan 2021 at 16:09, Nathan Stratton Treadway wrote: > On Wed, Jan 20, 2021 at 14:22:02 +1100, Tom Robin

Re: amgtar: defaults for NORMAL and STRANGE

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.mo

Re: amgtar: defaults for NORMAL and STRANGE

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 > &g

Re: amgtar: defaults for NORMAL and STRANGE

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: [...]

Re: amanda 3.5 (debian) - multiple instances - is it normal?

Jean-Louis Martineau writes: > amanda-3.5 allow to run multiple backup in parallel. > This to allow to run different amdump on different host/dle at the same time > and to allow client initiated backup to run at the same time. > > Jean-Louis Yes, I have read about it,

Re: amanda 3.5 (debian) - multiple instances - is it normal?

instances simultaneously. But recently I saw that exists two amdump processes dumping the same disk (although to different holiding disk). This is normal? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ <http://wolnelektury.pl/wesprzyj/teraz/> To kick or not to kick... -- Somewhere on IRC, in

amanda 3.5 (debian) - multiple instances - is it normal?

So far amanda was unable to run multiple instances simultaneously. But recently I saw that exists two amdump processes dumping the same disk (although to different holiding disk). This is normal? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ To kick or not to kick... -- Somewhere

amrecover works, normal amanda backup, logging connection refused

Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza amanda file in it. An ls -lau shows that file,

Re: amrecover works, normal amanda backup, logging connection refused

Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014: Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza amanda file in it. An

Re: amrecover works, normal amanda backup, logging connection refused

Gene, On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d but it has an old-xinetd.d

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply: Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014: Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 11:34:16 Olivier Nicole did opine And Gene did reply: Gene, On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the

Re: amrecover works, normal amanda backup, logging connection refused

On 07/18/2014 11:39 AM, Gene Heskett wrote: On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply: Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014: Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box,

Re: amrecover works, normal amanda backup, logging connection refused

On 07/18/2014 11:43 AM, Gene Heskett wrote: On Friday 18 July 2014 11:34:16 Olivier Nicole did opine And Gene did reply: Gene, On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the

RE: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett Sent: Friday, July 18, 2014 10:39 AM To: amanda-users@amanda.org Subject: [BULK] Re: amrecover works, normal amanda backup, logging connection refused On Friday 18 July 2014 10:50:47 John

Re: amrecover works, normal amanda backup, logging connection refused

On Fri, 18 Jul 2014 22:34:16 +0700 Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: What do I check next? Firewall? That's bitten me more than once. -- The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not

Re: amrecover works, normal amanda backup, logging connection refused

There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts BUT, in /etc/.amandahosts. I'll mv it to /etc/amandahosts. Ran amcheck, no change and that file was not accessed. The actual file SHOULD have a dot at the beginning of the name. .amandahosts I guess if the one

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 11:53:57 Jean-Louis Martineau did opine And Gene did reply: On 07/18/2014 11:39 AM, Gene Heskett wrote: On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply: Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014: Trying to figure out why amanda

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 11:54:51 Jean-Louis Martineau did opine And Gene did reply: On 07/18/2014 11:43 AM, Gene Heskett wrote: On Friday 18 July 2014 11:34:16 Olivier Nicole did opine And Gene did reply: Gene, On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote:

Re: amrecover works, normal amanda backup, logging connection refused

here is normal. Olivier

Re: amrecover works, normal amanda backup, logging connection refused

What do I check next? Thank you. Cheers, Gene Heskett Since Olivier wrote that he only used xinetd once, I figured I’d best chime in. I use it all the time (not that I know very much about it). Here are parts of my CHECKLIST for a new node: yum install openssh-server yum install

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

] Re: amrecover works, normal amanda backup, logging connection refused On Friday 18 July 2014 10:50:47 John Hein did opine And Gene did reply: Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014: Trying to figure out why amanda can't backup this machine, one of the things I noticed

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 12:10:10 Charles Curley did opine And Gene did reply: On Fri, 18 Jul 2014 22:34:16 +0700 Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: What do I check next? Firewall? That's bitten me more than once. No firewalls running on any machine, I have a dd-wrt

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 12:11:24 Debra S Baddorf did opine And Gene did reply: There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts BUT, in /etc/.amandahosts. I'll mv it to /etc/amandahosts. Ran amcheck, no change and that file was not accessed. The actual file

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 12:11:24 Debra S Baddorf did opine And Gene did reply: There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts BUT, in /etc/.amandahosts. I'll mv it to /etc/amandahosts. Ran amcheck, no change and that file was not accessed. The actual file

Re: amrecover works, normal amanda backup, logging connection refused

is normal. Olivier Ok, good to know. That maybe leaves .amandahosts? But neither of them are being touched by the amcheck, so its earlier in the attempt by my deduction. Thanks. Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo

Re: amrecover works, normal amanda backup, logging connection refused

Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014: 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address already in use (errno = 98)). service = amanda More than one xinetd or inetd running? Maybe some basic background is in order. The basic operation of *inetd is pretty

Re: amrecover works, normal amanda backup, logging connection refused

On Fri, Jul 18, 2014 at 10:26:38AM -0400, Gene Heskett wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d but it has an old-xinetd.d with a single

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 13:24:12 Debra S Baddorf did opine And Gene did reply: What do I check next? Thank you. Cheers, Gene Heskett Since Olivier wrote that he only used xinetd once, I figured I’d best chime in. I use it all the time (not that I know very much about it). Here

Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote: 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address already in use (errno = 98)). service = amanda 14/7/18@12:09:37: ERROR: 3859 {cnf_start_services} Service amanda failed to start and is deactivated.

RE: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

then... -- Joi Owen System Administrator Pavlov Media, Inc -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett Sent: Friday, July 18, 2014 1:36 PM To: amanda-users@amanda.org Subject: [BULK] Re: amrecover works, normal amanda backup

Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 1:35 PM, Gene Heskett ghesk...@wdtv.com wrote: backup user on the server is amanda, but neither client machine even has an amanda (or backup) user. Presumably its backup:backup on the clients. The /var/backups/.amandahosts files were different, so I made the failing

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 14:27:20 Jon LaBadie did opine And Gene did reply: On Fri, Jul 18, 2014 at 10:26:38AM -0400, Gene Heskett wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 14:51:39 Debra S Baddorf did opine And Gene did reply: On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote: 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address already in use (errno = 98)). service = amanda 14/7/18@12:09:37: ERROR: 3859

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett Sent: Friday, July 18, 2014 1:36 PM To: amanda-users@amanda.org Subject: [BULK] Re: amrecover works, normal amanda backup, logging connection refused On Friday 18 July 2014 13:24:12 Debra S Baddorf

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote: I think you have a more basic network connectivity issue. If it were a simple .amandahosts issue, you'd get an error message to that affect, not 'connection reset by peer', which is a network thing. Don't forget to

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 15:06:49 Debra S Baddorf did opine And Gene did reply: On Jul 18, 2014, at 1:35 PM, Gene Heskett ghesk...@wdtv.com wrote: backup user on the server is amanda, but neither client machine even has an amanda (or backup) user. Presumably its backup:backup on the clients.

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote: Don't forget to check the logs on the server and the client, see /var/log/Amanda/*, find the newest files in there and see what they say. do a locate(or a find / -iname “*am*” ) to find your amanda logs. Joi

Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 2:13 PM, Gene Heskett ghesk...@wdtv.com wrote: On Friday 18 July 2014 14:51:39 Debra S Baddorf did opine And Gene did reply: On Jul 18, 2014, at 11:25 AM, Gene Heskett ghesk...@wdtv.com wrote: 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address already

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 15:24:00 Debra S Baddorf did opine And Gene did reply: On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote: I think you have a more basic network connectivity issue. If it were a simple .amandahosts issue, you'd get an error message to that

Re: [BULK] Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 15:38:36 Debra S Baddorf did opine And Gene did reply: On Jul 18, 2014, at 1:53 PM, Joi L. Ellis jlel...@pavlovmedia.com wrote: Don't forget to check the logs on the server and the client, see /var/log/Amanda/*, find the newest files in there and see what they say.

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 15:49:47 Debra S Baddorf did opine And Gene did reply: ps auxww | grep net Except for PID's both machines are identical: shop: gene@shop:/etc$ ps auxww | grep net root13 0.0 0.0 0 0 ?SJul11 0:00 [netns] root 1128 0.0 0.0 1984

Re: amrecover works, normal amanda backup, logging connection refused

Gene Heskett gheskett-at-wdtv.com |amusersj-ml0| wrote at 15:07 -0400 on Jul 18, 2014: On Friday 18 July 2014 14:22:48 John Hein did opine And Gene did reply: Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014: 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address

Re: amrecover works, normal amanda backup, logging connection refused

On Friday 18 July 2014 16:16:15 John Hein wrote: Gene Heskett gheskett-at-wdtv.com |amusersj-ml0| wrote at 15:07 -0400 on Jul 18, 2014: On Friday 18 July 2014 14:22:48 John Hein did opine And Gene did reply: Gene Heskett wrote at 12:25 -0400 on Jul 18, 2014:

Re: amrecover works, normal amanda backup, logging connection refused

On Jul 18, 2014, at 3:13 PM, Gene Heskett ghesk...@wdtv.com wrote: On Friday 18 July 2014 15:49:47 Debra S Baddorf did opine And Gene did reply: ps auxww | grep net Except for PID's both machines are identical: shop: gene@shop:/etc$ ps auxww | grep net root13 0.0 0.0 0

Re: amrecover works, normal amanda backup, logging connection refused

to punching my ticket. Blew the right side of my heart up to about 2x normal, but that seems to have fixed itself now. The high priced clot-buster shot worked, so I am still here. Lost some weight too I feel better right now than I have in 10 years. On rat poison for blood thinner of course

Estimates taking two hours - is this normal?

to several hours? I just want to make sure that what I am seeing is normal. It seems like an awful lot of churning just to estimate a dump size. This happens to be my only Solaris system being backed up. On a linux system, I'm backing up an area approx. twice the size with no estimate timeouts. That may

Re: Estimates taking two hours - is this normal?

to have to bump up the estimate timeouts to several hours? I just want to make sure that what I am seeing is normal. It seems like an awful lot of churning just to estimate a dump size. This happens to be my only Solaris system being backed up. On a linux system, I'm backing up an area approx

amanda is working like normal again

There were no problems with amdump's level 0 run last night. sda10 backed-up along with the rest of my partitions. There was no power outage on any of the systems when sda10 failed to dump last weekend. I checked syslogs - etc. and found nothing. Thanks both to Chris and John for constant

normal?

in the middle for no apparent reason. I ran amcleanup and amflush and I noticed this line in the amflush log file, it happened when the taper ran out of tape, and I was wondering if the "ERR" was normal: taper: reader-side: got label WLCGNORM02 filenum 4 driver: send-cmd time 11183.111 to taper:

Re: normal?

was wondering if the "ERR" was normal: ... Yes, it's normal. It just means you banged into end of tape. There is no standard OS return code for that, so it comes up line to Amanda in many forms, usually as some type of I/O error. Robert Simmons John R. Jackson, Technical Software Speciali