Re: amanda fails

[Exuvo]

My wild guess looking at that file is that it is unable to read the inventory 
from the tapelist file?
If you are using autolabeling and this is a new empty backup configuration 
maybe you need to add the first tape manually.

Anton "exuvo" Olsson
   ex...@exuvo.se

On 2022-05-06 11:31, Stefan G. Weichinger wrote:

Am 18.10.21 um 14:38 schrieb Stefan G. Weichinger:


Anyone seeing this as well?


FAILURE DUMP SUMMARY:
   taper: FATAL Can't use an undefined value as an ARRAY reference at 
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/ScanInventory.pm line 343.

This on a debian-10.10 server


Hitting this again, now with debian 11.3

I assume this is some perl-issue, maybe related to upgrades inbetween.

Unfortunately I am still no perl-guru, maybe someone could have a look.

To me it seems related to the "taperscan"parameter.

Re: amanda fails

[Stefan G. Weichinger]

Am 18.10.21 um 14:38 schrieb Stefan G. Weichinger:


Anyone seeing this as well?


FAILURE DUMP SUMMARY:
   taper: FATAL Can't use an undefined value as an ARRAY reference at 
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/ScanInventory.pm line 343.


This on a debian-10.10 server


Hitting this again, now with debian 11.3

I assume this is some perl-issue, maybe related to upgrades inbetween.

Unfortunately I am still no perl-guru, maybe someone could have a look.

To me it seems related to the "taperscan"parameter.

Re: amanda fails

[Gene Heskett]

On Friday 12 November 2021 04:58:34 Olivier wrote:

> Gene Heskett  writes:
> > I should probably point out that ALL my problems with bad crc's of
> > the holding disk files went away when I replaced the holding disk,
> > which was apparently an SMR disk, with an SSD of 1/4 the size of the
> > spinning rust disk.  And my backup times to get all 6 machines were
> > sped up from around two hours to under 30 minutes. All by the
> > non-SMR, SSD holding disk.  So at the very least, I can sure
> > recommend an SSD as a holding disk.
>
> My 2 cents about using SSD for holding disk: over 15 years of running
> amanda on hard disks, the only disk problem I ever had was with the
> holding disk and the disk did get damaged in the holding disk area. It
> seems that the holding disk function puts a tremendous usage on the
> disk (especially with compression on the server I presume) to the
> point of damaging a hard disk. I am wondering how an SSD will cope.
>
Since the holding disk is empty at the end of a given run that had no 
errors, a hard drive will get beat up on the same area near the start of 
the disk. The SSD has 23+ hours to look things over and if needed, 
shuffle the data areas used all over its array. All while its 
essentially empty. Only 62k of 240 gigs is shown as used right now, and 
thats just the ext4 overheard.  Its empty now since thats all it does.
It will be a long time before the wear leveler can't find enough good 
sectors to do a backup. Since I'm 87, I expect it to outlast me.

> Best regards,
>
> Olivier



Copyright 2021 by Maurice E. Heskett
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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: amanda fails

[Olivier]

Gene Heskett  writes:

> I should probably point out that ALL my problems with bad crc's of the 
> holding disk files went away when I replaced the holding disk, which was 
> apparently an SMR disk, with an SSD of 1/4 the size of the spinning rust 
> disk.  And my backup times to get all 6 machines were sped up from 
> around two hours to under 30 minutes. All by the non-SMR, SSD holding 
> disk.  So at the very least, I can sure recommend an SSD as a holding 
> disk.

My 2 cents about using SSD for holding disk: over 15 years of running
amanda on hard disks, the only disk problem I ever had was with the
holding disk and the disk did get damaged in the holding disk area. It
seems that the holding disk function puts a tremendous usage on the disk
(especially with compression on the server I presume) to the point of
damaging a hard disk. I am wondering how an SSD will cope.

Best regards,

Olivier

Re: amanda fails

[Gene Heskett]

On Saturday 23 October 2021 05:03:23 Gene Heskett wrote:

> On Saturday 23 October 2021 04:52:41 Stefan G. Weichinger wrote:
> > Am 19.10.21 um 16:45 schrieb Charles Curley:
> > > On Tue, 19 Oct 2021 10:19:28 +0200
> > >
> > > "Stefan G. Weichinger"  wrote:
> > >> Switching the parameter "taperscan" from "lexical" to
> > >> "traditional" works around that now.
> > >
> > > I don't have taperscan in either of my configurations, so I guess
> > > I'm running on the default. The lack probably comes from more than
> > > a decade of copying in old configurations every time I install.
> >
> > That setup worked for a few days now with "traditional".
> >
> > Checked right now, holding disk full, dumps not taped again.
> >
> > amcheck did not find the next vtape, I assume the external USB drive
> > (= another chg-disk changer in my aggregate setup) has been plugged
> > in yesterday.
>
> But you don't know that for sure?  And is it automounted when it is
> plugged in? One of the things people do is forget...
>
> > Edited back to "lexical", amflush works now.
> >
> > A bit strange and not reliable, as it seems.

I should probably point out that ALL my problems with bad crc's of the 
holding disk files went away when I replaced the holding disk, which was 
apparently an SMR disk, with an SSD of 1/4 the size of the spinning rust 
disk.  And my backup times to get all 6 machines were sped up from 
around two hours to under 30 minutes. All by the non-SMR, SSD holding 
disk.  So at the very least, I can sure recommend an SSD as a holding 
disk.

It has been so successful and error free over the last 6 months, that I 
have installed, but not yet built for use, 4 1T samsung EVO-870 SSD's on 
another cheap non-raid controller, adding 6 more sata-III ports, which I 
intend to build a raid 10 out of, and use for the /home partition if and 
when I install debian 11. Probably when debian announces 11.3 as that 
should be time enough to fix any new bullseye version bugs.

Will that find something not compatible with amanda 3.5.1?

Copyright 2021 by Maurice E. Heskett
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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: amanda fails

[Gene Heskett]

On Saturday 23 October 2021 04:52:41 Stefan G. Weichinger wrote:

> Am 19.10.21 um 16:45 schrieb Charles Curley:
> > On Tue, 19 Oct 2021 10:19:28 +0200
> >
> > "Stefan G. Weichinger"  wrote:
> >> Switching the parameter "taperscan" from "lexical" to "traditional"
> >> works around that now.
> >
> > I don't have taperscan in either of my configurations, so I guess
> > I'm running on the default. The lack probably comes from more than a
> > decade of copying in old configurations every time I install.
>
> That setup worked for a few days now with "traditional".
>
> Checked right now, holding disk full, dumps not taped again.
>
> amcheck did not find the next vtape, I assume the external USB drive
> (= another chg-disk changer in my aggregate setup) has been plugged in
> yesterday.

But you don't know that for sure?  And is it automounted when it is 
plugged in? One of the things people do is forget...
>
> Edited back to "lexical", amflush works now.
>
> A bit strange and not reliable, as it seems.



Copyright 2019 by Maurice E. Heskett
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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: amanda fails

[Stefan G. Weichinger]

Am 19.10.21 um 16:45 schrieb Charles Curley:

On Tue, 19 Oct 2021 10:19:28 +0200
"Stefan G. Weichinger"  wrote:


Switching the parameter "taperscan" from "lexical" to "traditional"
works around that now.


I don't have taperscan in either of my configurations, so I guess I'm
running on the default. The lack probably comes from more than a decade
of copying in old configurations every time I install.


That setup worked for a few days now with "traditional".

Checked right now, holding disk full, dumps not taped again.

amcheck did not find the next vtape, I assume the external USB drive (= 
another chg-disk changer in my aggregate setup) has been plugged in 
yesterday.


Edited back to "lexical", amflush works now.

A bit strange and not reliable, as it seems.

Re: amanda fails

[Charles Curley]

On Tue, 19 Oct 2021 10:19:28 +0200
"Stefan G. Weichinger"  wrote:

> Switching the parameter "taperscan" from "lexical" to "traditional" 
> works around that now.

I don't have taperscan in either of my configurations, so I guess I'm
running on the default. The lack probably comes from more than a decade
of copying in old configurations every time I install.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: amanda fails

[Stefan G. Weichinger]

Am 18.10.21 um 18:00 schrieb Charles Curley:

On Mon, 18 Oct 2021 14:38:46 +0200
"Stefan G. Weichinger"  wrote:


Anyone seeing this as well?


FAILURE DUMP SUMMARY:
taper: FATAL Can't use an undefined value as an ARRAY reference at
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/ScanInventory.pm line
343.

This on a debian-10.10 server


Nope. Never seen it. I am using VTAPEs.


Updated to 10.11, no change.

Amanda does not dump or flush to tapes because of that error.

I am not aware of any changes to the amanda config lately.

Switching the parameter "taperscan" from "lexical" to "traditional" 
works around that now.


Although I remember that Jean-Louis told me back then to use "lexical" 
to make things work with my setup of aggregating multiple chg-disk changers.

Re: amanda fails

[Charles Curley]

On Mon, 18 Oct 2021 14:38:46 +0200
"Stefan G. Weichinger"  wrote:

> Anyone seeing this as well?
> 
> 
> FAILURE DUMP SUMMARY:
>taper: FATAL Can't use an undefined value as an ARRAY reference at 
> /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/ScanInventory.pm line
> 343.
> 
> This on a debian-10.10 server

Nope. Never seen it. I am using VTAPEs.

charles@hawk:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster
charles@hawk:~$ pre amanda
amanda-client   1:3.5.1-2+b2amd64
amanda-common   1:3.5.1-2+b2amd64
amanda-server   1:3.5.1-2+b2amd64
charles@hawk:~$ cat /etc/debian_version 
10.11
charles@hawk:~$ 




-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

amanda fails

[Stefan G. Weichinger]

Anyone seeing this as well?


FAILURE DUMP SUMMARY:
  taper: FATAL Can't use an undefined value as an ARRAY reference at 
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/ScanInventory.pm line 343.


This on a debian-10.10 server

amanda fails to backup regular files.

[Sal Sharief]

I am running into a situation where amanda fails to
backup regular files although it maintains the
directory structure. Anyone ran into this kind of problem?




__
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

Re: amanda fails to backup regular files.

[Jon LaBadie]

On Fri, Jun 11, 2004 at 07:01:21AM -0700, Sal Sharief wrote:
 I am running into a situation where amanda fails to
 backup regular files although it maintains the
 directory structure. Anyone ran into this kind of problem?

I did a long time ago when I was using a cygwin version of amanda.

More info about your environment and versions please, including
the version of gnutar being used on the client.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: amanda fails to backup regular files.

[Paul Bijnens]

Sal Sharief wrote:
I am running into a situation where amanda fails to
backup regular files although it maintains the
directory structure. Anyone ran into this kind of problem?
Never seen.
How did you come that conclusion?
What OS?
What backupprogram?
Debug files?
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***

amanda fails after upgrade

[Ted Sariyski]

Hi,

I upgraded one of the i386 hosts to RedHat 7.2  and now the server 
running amanda  amanda-2.4.1p1 returns an error:

WARNING: xtreme19: selfcheck request timed out.  Host down?

The amanda client log file amandad..debug ends with:

amandad: error [getpwuid(33) fails]
error [getpwuid(33) fails]

What does it mean?

Thanks in advance,
Ted


amandad: debug 1 pid 21482 ruid 33 euid 33 start time Thu Jan 24 07:18:04 2002
amandad: version 2.4.2p2
amandad: build: VERSION=Amanda-2.4.2p2
amandad:BUILT_DATE=Fri Jul 13 18:48:49 EDT 2001
amandad:BUILT_MACH=Linux stripples.devel.redhat.com 2.4.5-10enterprise #1 SMP 
Wed Jun 27 14:01:18 EDT 2001 i686 unknown
amandad:CC=gcc
amandad: paths: bindir=/usr/bin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda
amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/
amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient
amandad:GNUTAR=/bin/tar COMPRESS_PATH=/usr/bin/gzip
amandad:UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost
amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
got packet:

Amanda 2.4 REQ HANDLE 006-60850508 SEQ 1011885348
SECURITY USER amanda
SERVICE selfcheck
OPTIONS ;
GNUTAR /home82 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/etc/amanda/exclude;
GNUTAR /usr/pgi 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/etc/amanda/exclude;
GNUTAR /usr/local 0 OPTIONS 
|;bsd-auth;index;exclude-list=/usr/local/etc/amanda/exclude;
GNUTAR / 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/etc/amanda/exclude;

 
sending ack:

Amanda 2.4 ACK HANDLE 006-60850508 SEQ 1011885348

 
amandad: error [getpwuid(33) fails]
error [getpwuid(33) fails]
amandad: pid 21482 finish time Thu Jan 24 07:18:04 2002

Re: amanda fails after upgrade

[Joshua Baker-LePain]

On Thu, 24 Jan 2002 at 10:26am, Ted Sariyski wrote

 The amanda client log file amandad..debug ends with:
 
 amandad: error [getpwuid(33) fails]
 error [getpwuid(33) fails]
 
Did you remember to add the amanda user?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: amanda fails after upgrade

[Joshua Baker-LePain]

On Thu, 24 Jan 2002 at 11:03am, Ted Sariyski wrote

 Joshua Baker-LePain wrote:
 
 Did you remember to add the amanda user?

 Yes,

 Even I can rsh from the server to the client without a password.
 
And is the UID the same as it was before?

Did you do a upgrade install, or did you wipe the filesystems and start 
over?

(P.S. Please keep amanda-users on the cc list, so everyone can help out.)

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

RE: amanda fails after upgrade

[Dan Garthwaite]

Sounds like a firewall to me:
  /etc/init.d/ipchains stop
  /etc/init.d/iptables stop

-dan

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Joshua Baker-LePain
 Sent: Thursday, January 24, 2002 1:30 PM
 To: Ted Sariyski
 Cc: [EMAIL PROTECTED]
 Subject: Re: amanda fails after upgrade
 
 
 On Thu, 24 Jan 2002 at 11:03am, Ted Sariyski wrote
 
  Joshua Baker-LePain wrote:
  
  Did you remember to add the amanda user?
 
  Yes,
 
  Even I can rsh from the server to the client without a password.
  
 And is the UID the same as it was before?
 
 Did you do a upgrade install, or did you wipe the 
 filesystems and start 
 over?
 
 (P.S. Please keep amanda-users on the cc list, so everyone 
 can help out.)
 
 -- 
 Joshua Baker-LePain
 Department of Biomedical Engineering
 Duke University
 
 
 

Re: every 10 days amanda fails

[Chris Marble]

=?iso-8859-1?Q?gloria_era=F1a?= wrote:
 
 I've been noticing that our amanda backup fails every 10 days and stop to
 backup our main server. Can someone point me why I'm getting this? I'm not
 very familiar with amanda and we rely on someone's script for our backup
 which makes it more complicated. I would appreciate for any help. Thanks.

Is your dumpcycle 10?  Does your disklist specify a 10-day cycle for
any particular drives (actually a special dumptype specified in amanda.conf)?
I expect there's some disk that's getting a full backup every 10 days and
there's a problem with it or the connectivity to that computer).
-- 
  [EMAIL PROTECTED] - HMC UNIX Systems Manager
  My opinions are my own and probably don't represent anything anyway.

Amanda fails to build: amoverview

[ROD]

I just got around to installing Amanda-2.4.2 stable unfortunately I can't
get it to build on FreeBSD 4.11.  The following error is reported:

make: don't know how to make amoverview. Stop
*** Error code 1

Any help would be appreciated

Best regards

Rod

Re: Amanda fails to build: amoverview

[David Wolfskill]

From: "ROD" [EMAIL PROTECTED]
Date: Tue, 19 Dec 2000 15:36:31 -

I just got around to installing Amanda-2.4.2 stable unfortunately I can't
get it to build on FreeBSD 4.11.  The following error is reported:

make: don't know how to make amoverview. Stop
*** Error code 1

Any help would be appreciated

Please see http://www.egroups.com/message/amanda-hackers/2333 (and
following thread).

(Summary:  yes; appears to be a problem with FreeBSD make; see
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23328 for that part.  A
circumvention is to hack the Makefiles; another is to use gmake.)

Cheers,
david
-- 
David Wolfskill  [EMAIL PROTECTED]   UNIX System Administrator
Desk: 650/577-7158   TIE: 8/499-7158   Cell: 650/759-0823