Re: Release of amanda-2.5.0b2
On Thu, Jan 19, 2006 at 07:31:08PM -0500, Jean-Louis Martineau wrote: > The Amanda core team is pleased to announce the release of Amanda > 2.5.0b2. It is stable and we hope to release 2.5.0 soon. test it and > report it if you find a bug in this release. The mail reports that are mailed by amdump have bogus numbers in the MMM:SS columns. For example: this line comes from the logfile: SUCCESS dumper host.do.main /m/b 20060222 2 [sec 115.740 kb 142504 kps 1231.2 orig-kb 521380] SUCCESS chunker host.do.main /m/b 20060222 2 [sec 115.822 kb 142504 kps 1230.6] And this is what the mail contains: STATISTICS: Run Time (hrs:min) 0:14 DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-MB OUT-MB COMP% CRYPT% MMM:SS KB/s MMM:SS KB/s - host.do.main /m/b 2 509139 27.3 1:561231.2 N/A N/A The real dump duration was about 115 seconds, but amdump says 1231.2 minutes. Note that the "kps" filed in the logfile contains the value that is reported my the mail.
Re: compile fail on Soalris 10 X86/AMD64
On Tue, Feb 21, 2006 at 07:18:37PM -0500, stan wrote: > > I'v got a brand spanking new Ultra 40, just for running Amanda! I', > trhilled. > > But, I seem to be having a problem geting either the stable version, or the > latest 2.5 bersion to build coreclty. here's a logfile from the stable > build. > > > Script started on Tue Feb 21 18:57:19 2006 > [EMAIL PROTECTED] # make ... > gcc -shared -Wl,-h -Wl,libamanda-2.4.5p1.so -o .libs/libamanda-2.4.5p1.so = > =2Elibs/alloc.o .libs/amflock.o .libs/clock.o .libs/debug.o .libs/dgram.o .= > libs/error.o .libs/file.o .libs/fileheader.o .libs/amfeatures.o .libs/match= > =2Eo .libs/protocol.o .libs/regcomp.o .libs/regerror.o .libs/regexec.o .lib= > s/regfree.o .libs/security.o .libs/statfs.o .libs/stream.o .libs/token.o .l= > ibs/util.o .libs/versuff.o .libs/version.o .libs/pipespawn.o .libs/sl.o -l= > gen -lm -ltermcap -lsocket -lnsl -lintl -lc=20 > (cd .libs && rm -f libamanda.so && ln -s libamanda-2.4.5p1.so libamanda.so) | v > false cru .libs/libamanda.a alloc.o amflock.o clock.o debug.o dgram.o erro= > r.o file.o fileheader.o amfeatures.o match.o protocol.o regcomp.o regerror.= > o regexec.o regfree.o security.o statfs.o stream.o token.o util.o versuff.o= > version.o pipespawn.o sl.o > *** Error code 1 > make: Fatal error: Command failed for target `libamanda.la' The command "false" should have been "ar", the "archive" command used to build and extract from libraries. Likely you are running some release of Sol 10 and I'm unfamiliar with that. In Sol 9 x86 "ar" is found in /usr/xpg4/bin and in /usr/ccs/bin. A guess, when you ran configure the directory containing ar was not in your PATH, configure couldn't find ar and thus used the false command instead. Your Makefile probably contains a line like AR = /usr/bin/false . -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
compile fail on Soalris 10 X86/AMD64
I'v got a brand spanking new Ultra 40, just for running Amanda! I', trhilled. But, I seem to be having a problem geting either the stable version, or the latest 2.5 bersion to build coreclty. here's a logfile from the stable build. Script started on Tue Feb 21 18:57:19 2006 [EMAIL PROTECTED] # make Making all in config make all-am Making all in common-src source=3D'alloc.c' object=3D'alloc.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o alloc.lo all= oc.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c alloc.c -fPIC -DPIC -o .libs/alloc.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c alloc.c -o alloc.o >/dev/null 2>&1 source=3D'amflock.c' object=3D'amflock.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o amflock.lo a= mflock.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c amflock.c -fPIC -DPIC -o .libs/amflock.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c amflock.c -o amflock.o >/dev/null 2>&1 source=3D'clock.c' object=3D'clock.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o clock.lo clo= ck.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c clock.c -fPIC -DPIC -o .libs/clock.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c clock.c -o clock.o >/dev/null 2>&1 source=3D'debug.c' object=3D'debug.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o debug.lo deb= ug.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c debug.c -fPIC -DPIC -o .libs/debug.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c debug.c -o debug.o >/dev/null 2>&1 source=3D'dgram.c' object=3D'dgram.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o dgram.lo dgr= am.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c dgram.c -fPIC -DPIC -o .libs/dgram.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c dgram.c -o dgram.o >/dev/null 2>&1 source=3D'error.c' object=3D'error.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/bash ../libtool --tag=3DCC --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -= I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D= 64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g -O2 -c -o error.lo err= or.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c error.c -fPIC -DPIC -o .libs/error.o gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOUR= CE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -g= -O2 -c error.c -o error.o >/dev/null 2>&1 source=3D'file.c' object=3D'file.lo' libtool=3Dyes \ DEPDIR=3D.deps depmode=3Dnone /bin/bash ../config/depcomp \ /bin/ba
Re: Problems with amrestore - please HELP
Hi, Maybe this is some issue with encryption? not likely. Data encryption is new to Amanda 2.5.0.2. amrestore sends all warnings/error to stderr. Try "amrestore -f 0 ..." and send us the stderr output. Maybe rpm package was compiled with it? I dont know how to check it . "amadmin config_name version" will tell you the flags that are configured in. --Kevin Till -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Self check failing
Lengyel, Florian wrote: I'm getting an amanda self-check failure from amcheck daily: I suppose this was due to the mysterious disconnect of one server (m248)... another one (nept) is running, but after removing a duplicate uid for amanda in the NIS maps, it stopped working. Amanda Backup Client Hosts Check WARNING: nept.gc.cuny.edu: selfcheck request timed out. Host down? WARNING: m248.gc.cuny.edu: selfcheck request timed out. Host down? Hi, do you use xinetd? If so, try to restart it and see if there is any error message to the syslog. Looks like amcheck cannot connect to amandad on the client. WARNING: rdhcp: selfcheck reply timed out. WARNING: m254.gc.cuny.edu: selfcheck reply timed out. WARNING: amanda: selfcheck reply timed out. Client check: 8 hosts checked in 100.158 seconds, 5 problems found (brought to you by Amanda 2.4.4p3) -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: gzip trailing garbage
Greg Troxel wrote: I'm using 2.4.5p1 on NetBSD with Kerberos encryption and authentication. I tried to verify some tapes and found that 'gzip -t' failed on the restored files. On investigation, after adding some better diagnostics to gzip (NetBSD's own), I found that the problem was that the last 32K block was padded with zeros. Unflushed dumps in the holding directory have this problem for remote dumps (krb encrypted), but not local ones. On an older amanda install, not using krb4, I don't have this problem. Is anyone else seeing this? Hi Greg, Yes, I have seen it with the new data encryption in Amanda 2.5. gzip will ignore the trailing zero and give out advisory about trailing garbage. While bzip2 does not ignore trailing zeros. I have yet found out what part of Amanda code is responsible for the trailing zeros though. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Problems with amrestore - please HELP
What do the log files say? They are usually in /tmp/amanda/ on the server. Thanks tk Radek Cisz wrote: Hello everyone, please advice... I have two servers. One for production and second as backup. Both have streamers that read LTO tapes. On these servers I have installed Suse 9.0 and amanda from rpm package. When I do backup with amanda on production server , then I can restore it on the same production server without any problems. But when I try to restore it on backup server I got message that backup is not dump or tar type (I understand these issues and do dump backup) The same is on backup server. When i do backup on it, then I can restore on localhost, but can not restore on production server (the same messages) These restors are not by network, then local restoration from streamer... Maybe this is some issue with encryption? Maybe rpm package was compiled with it? I dont know how to check it ... Does anyone has any ideas??? Regards Radek -- Ram "TK" Krishnamurthy http://www.zmanda.com
Problems with amrestore - please HELP
Hello everyone, please advice... I have two servers. One for production and second as backup. Both have streamers that read LTO tapes. On these servers I have installed Suse 9.0 and amanda from rpm package. When I do backup with amanda on production server , then I can restore it on the same production server without any problems. But when I try to restore it on backup server I got message that backup is not dump or tar type (I understand these issues and do dump backup) The same is on backup server. When i do backup on it, then I can restore on localhost, but can not restore on production server (the same messages) These restors are not by network, then local restoration from streamer... Maybe this is some issue with encryption? Maybe rpm package was compiled with it? I dont know how to check it ... Does anyone has any ideas??? Regards Radek
gzip trailing garbage
I'm using 2.4.5p1 on NetBSD with Kerberos encryption and authentication. I tried to verify some tapes and found that 'gzip -t' failed on the restored files. On investigation, after adding some better diagnostics to gzip (NetBSD's own), I found that the problem was that the last 32K block was padded with zeros. Unflushed dumps in the holding directory have this problem for remote dumps (krb encrypted), but not local ones. On an older amanda install, not using krb4, I don't have this problem. Is anyone else seeing this? Does GNU gzip ignore trailing NULLs? The NetBSD implementation goes back to looking for MAGIC0 after reading the saved length. -- Greg Troxel <[EMAIL PROTECTED]>
Re: request failed: timeout waiting for ACK
On Tue, Feb 21, 2006 at 09:45:32AM +0100, Stefan Herrmann wrote: > hello list, > > i made a fresh install of "Amanda 2.5.0b2" on a debian 3.1 system. then > i set up amanda for a hourly backup. > i did some test backups that worked ok. then i mentioned an error in > the amanda.conf and aborted the dump > manually. stopped all amanda processes on the client manually and > corrected the error. since then i get lots of > "(aborted:[request failed: timeout waiting for ACK])(too many dumper > retry)" when doing backups: > Anytime I hear "manually stopped", my first question is: have you run amcleanup on server and client? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Still get ERROR [host fw.my.co.uk: port 62679 not secure]
On 2006-02-21 11:02, Chuck Amadi Systems Administrator wrote: Here is the output from the server client debug I have since changed the Estimate timeout parameter from 300 to " etimeout 380 " on my ~tape server/amanda.conf Thus doubled the amandad: time 180.183: dgram_recv in debug report. amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 003-30610808 SEQ 1140464706 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=server.my.co.uk; GNUTAR / 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-30610808 SEQ 1140464706 amandad: time 0.053: bsd security: remote host fw.my.co.uk user amanda local user amanda amandad: time 0.053: amandahosts security check passed amandad: time 0.053: running service "/usr/local/libexec/sendsize" amandad: time 170.173: sending REP packet: Amanda 2.4 REP HANDLE 003-30610808 SEQ 1140464706 OPTIONS features=feff9ffe0f; / 0 SIZE 5006670 amandad: time 180.183: dgram_recv: timeout after 10 seconds I think that is because the masquerading time for udp packets in the ipchains firewall has been exceeded. The first ACK did work, it is the one taking 170 seconds that times out. Change it by executing on the firewall: ipchains -M -S tcp tcpfin udp Filling in 0 means "do not change the value": ipchains -M -S 0 0 300 (I did not use ipchains since more than 4 or 5 years now, so take care and read the man page again too.) -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: request failed: timeout waiting for ACK
Hi Have you had a look at your amanda tape server amanda.conf file and amending the etimeout parameter default is usually 300 seconds. I run less command on /tmp/amanda/amanda-date-.debug and my client was timing out on 180.33 seconds So I had read a good possibility is that udp which is stateless is taken to my time and hences times out. Worth a try I hope it helps I have a similar problem amcheck states no errors found but whem amdump tries to do it's thing I get a timeout error as below: amandad: time 180.183: dgram_recv in debug report. So I am googggling around and reading amanda mailing list for a solution to my issue I am nearly there. All the best. On Tue, 2006-02-21 at 09:45 +0100, Stefan Herrmann wrote: > hello list, > > i made a fresh install of "Amanda 2.5.0b2" on a debian 3.1 system. then > i set up amanda for a hourly backup. > i did some test backups that worked ok. then i mentioned an error in > the amanda.conf and aborted the dump > manually. stopped all amanda processes on the client manually and > corrected the error. since then i get lots of > "(aborted:[request failed: timeout waiting for ACK])(too many dumper > retry)" when doing backups: > > [EMAIL PROTECTED]:~$ amstatus hourly > Using /usr/local/etc/amanda/hourly/amdump.1 from Tue Feb 21 09:22:36 > CET 2006 > > pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout > waiting for ACK])(too many dumper retry) > pille.hq.imos.net:/opt 0 driver: (aborted:[request failed: timeout > waiting for ACK])(too many dumper retry) > pille.hq.imos.net:/usr 0 driver: (aborted:[request failed: timeout > waiting for ACK])(too many dumper retry) > pille.hq.imos.net:/var 1 45m finished (9:28:16) > > SUMMARY part real estimated > size size > partition : 4 > estimated : 455036m > flush : 0 0m > failed : 355015m ( 99.96%) > wait for dumping: 00m ( 0.00%) > dumping to tape : 00m ( 0.00%) > dumping : 0 0m 0m ( 0.00%) ( 0.00%) > dumped : 145m20m (220.31%) ( 0.08%) > wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) > wait to flush : 0 0m 0m (100.00%) ( 0.00%) > writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) > failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) > taped : 145m20m (220.31%) ( 0.08%) >tape 1: 145m20m ( 0.04%) hourly009 > 6 dumpers idle : no-dumpers > taper idle > network free kps: 14000 > holding space :258607m (100.00%) > chunker0 busy : 0:00:00 ( 0.00%) > dumper0 busy : 0:03:10 ( 36.36%) > taper busy : 0:00:02 ( 0.55%) > 0 dumpers busy : 0:08:37 ( 98.82%)not-idle: 0:05:31 ( > 64.11%) > client-constrained: 0:02:01 ( > 23.49%) > start-wait: 0:00:34 ( > 6.57%) > no-dumpers: 0:00:30 ( > 5.83%) > 1 dumper busy : 0:00:05 ( 1.05%) start-wait: 0:00:05 ( > 99.46%) > > i already rebooted the amanda server and cant find any more processes > running on the client. also did a restart of > inetd on the client. > > does anyone have a clue whats the problem ? os what this abort message > means ? > > thanks and by > Stefan Herrmann > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Self check failing
Title: Self check failing I'm getting an amanda self-check failure from amcheck daily: I suppose this was due to the mysterious disconnect of one server (m248)... another one (nept) is running, but after removing a duplicate uid for amanda in the NIS maps, it stopped working. Amanda Backup Client Hosts Check WARNING: nept.gc.cuny.edu: selfcheck request timed out. Host down? WARNING: m248.gc.cuny.edu: selfcheck request timed out. Host down? WARNING: rdhcp: selfcheck reply timed out. WARNING: m254.gc.cuny.edu: selfcheck reply timed out. WARNING: amanda: selfcheck reply timed out. Client check: 8 hosts checked in 100.158 seconds, 5 problems found (brought to you by Amanda 2.4.4p3)
Re: Problems with amrecover in 2.4.5p1
Paul Bijnens wrote: On 2006-02-21 09:25, Stephen Carville wrote: My attempt to restore files with amrecover keep failing since I upgraded to 2.4.5. The output in amidxtaped.debug looks like: amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 [...] amrestore: could not open /dev/ait2: Permission denied amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission denied amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006 My first question then is, what are the permissions of /dev/ait2, and what are the user/group you are using for starting amidxtaped in (x)inetd. Sound of palm slapping forhead...That was it. /dev/ait2 is a symlink to /dev/nst0. I checked the old server and the permissions there were: crw-rw-r--1 root disk 9, 128 Aug 30 2001 /dev/nst0 On the new server: crw-rw 1 root disk 9, 128 Feb 19 11:53 /dev/nst0 Once I added the global read, amrecover worked again. I don't know how many time I looked at those permissions wihtseeing the problem. Thanks -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
Re: Still get ERROR [host fw.my.co.uk: port 62679 not secure]
Hi List This morning I got my AMANDA MAIL REPORT and server had failed. Thus I have less /tmp/amanda/amandad.20060220210110.debug Here is the output from the server client debug I have since changed the Estimate timeout parameter from 300 to " etimeout 380 " on my ~tape server/amanda.conf Thus doubled the amandad: time 180.183: dgram_recv in debug report. amandad: RDEV_PREFIX="/dev/" DUMP=UNDEF RESTORE=UNDEF VDUMP=UNDEF amandad: VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF amandad: VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR="/bin/tar" amandad: COMPRESS_PATH="/usr/bin/gzip" amandad: UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lpr" amandad: MAILER="/usr/bin/Mail" amandad: listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="server" DEFAULT_CONFIG="DailySet1" amandad: DEFAULT_TAPE_SERVER="server" 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" amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 003-30610808 SEQ 1140464706 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=server.my.co.uk; GNUTAR / 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-30610808 SEQ 1140464706 amandad: time 0.053: bsd security: remote host fw.my.co.uk user amanda local user amanda amandad: time 0.053: amandahosts security check passed amandad: time 0.053: running service "/usr/local/libexec/sendsize" amandad: time 170.173: sending REP packet: Amanda 2.4 REP HANDLE 003-30610808 SEQ 1140464706 OPTIONS features=feff9ffe0f; / 0 SIZE 5006670 amandad: time 180.183: dgram_recv: timeout after 10 seconds amandad: time 180.194: waiting for ack: timeout, retrying amandad: time 190.193: dgram_recv: timeout after 10 seconds amandad: time 190.193: waiting for ack: timeout, retrying amandad: time 200.193: dgram_recv: timeout after 10 seconds amandad: time 200.193: waiting for ack: timeout, retrying amandad: time 210.193: dgram_recv: timeout after 10 seconds amandad: time 210.193: waiting for ack: timeout, retrying amandad: time 220.193: dgram_recv: timeout after 10 seconds amandad: time 223.994: waiting for ack: timeout, giving up! amandad: time 223.994: pid 29022 finish time Mon Feb 20 21:04:54 2006 amandad.20060220210110.debug lines 12-61/61 (END) Thus is there anything else I can do as amcheck is working but amdump which I believe is the issue relating to TCP but I have ports open on my firewall 10080:10083 I have also read that via MAILING LIST - *Mailing List Blurb *** It seems that the client receives an ACK, but the ACK is not what the client thinks it ought to be. After that it times out. *** Cheers for you help. On Mon, 2006-02-20 at 15:03 +0100, Paul Bijnens wrote: > On 2006-02-20 14:51, Chuck Amadi Systems Administrator wrote: > > Amanda Backup Client Hosts Check > > > > ERROR: server.my.co.uk: [access as amanda not allowed from [EMAIL PROTECTED] > > co.uk] open of /home/amanda/.amandahosts failed > > Client check: 4 hosts checked in 10.078 seconds, 1 problem found > > > > I created a dir and file /var/lib/amanda/.amandahosts file I have of > > course not got a /home/amanda/.amandahosts on my fw.my.co.uk server So > > should I created a user and the necessary dir and files. > > What is the home directory of the user Amanda? i.e. what is > the sixth field in /etc/passwd of that client (not the server!)? > > So on that client, add the next line to the .amandahosts file: > > amanda fw.my.co.uk > > > > > > > Thus added to .amandahosts file: > > I haven't create a user amanda or group disk Yet But am I on the right > > track with this new amacheck error. > > > > localhost amanda > > localhost root > > server.my.co.uk amanda > > server.my.co.uk root > > tape-server.myl.co.uk amanda > > tape-server.my.co.uk root > > See also: > > > http://wiki.zmanda.com/index.php/Amcheck:_access_as_localuser_not_allowed_from_remoteuser%40remotehost > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
request failed: timeout waiting for ACK
hello list, i made a fresh install of "Amanda 2.5.0b2" on a debian 3.1 system. then i set up amanda for a hourly backup. i did some test backups that worked ok. then i mentioned an error in the amanda.conf and aborted the dump manually. stopped all amanda processes on the client manually and corrected the error. since then i get lots of "(aborted:[request failed: timeout waiting for ACK])(too many dumper retry)" when doing backups: [EMAIL PROTECTED]:~$ amstatus hourly Using /usr/local/etc/amanda/hourly/amdump.1 from Tue Feb 21 09:22:36 CET 2006 pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/opt 0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/usr 0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/var 1 45m finished (9:28:16) SUMMARY part real estimated size size partition : 4 estimated : 455036m flush : 0 0m failed : 355015m ( 99.96%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 145m20m (220.31%) ( 0.08%) wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 145m20m (220.31%) ( 0.08%) tape 1: 145m20m ( 0.04%) hourly009 6 dumpers idle : no-dumpers taper idle network free kps: 14000 holding space :258607m (100.00%) chunker0 busy : 0:00:00 ( 0.00%) dumper0 busy : 0:03:10 ( 36.36%) taper busy : 0:00:02 ( 0.55%) 0 dumpers busy : 0:08:37 ( 98.82%)not-idle: 0:05:31 ( 64.11%) client-constrained: 0:02:01 ( 23.49%) start-wait: 0:00:34 ( 6.57%) no-dumpers: 0:00:30 ( 5.83%) 1 dumper busy : 0:00:05 ( 1.05%) start-wait: 0:00:05 ( 99.46%) i already rebooted the amanda server and cant find any more processes running on the client. also did a restart of inetd on the client. does anyone have a clue whats the problem ? os what this abort message means ? thanks and by Stefan Herrmann
Re: Problems with amrecover in 2.4.5p1
On 2006-02-21 09:25, Stephen Carville wrote: My attempt to restore files with amrecover keep failing since I upgraded to 2.4.5. The output in amidxtaped.debug looks like: amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 [...] amrestore: could not open /dev/ait2: Permission denied amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission denied amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006 My first question then is, what are the permissions of /dev/ait2, and what are the user/group you are using for starting amidxtaped in (x)inetd. This makes no sense to me since I was able to recover the files using amrestore on the server. amrestore runs as root, but amidxtaped runs as amanda usually. If the permissions of /dev/ait2 are group readable, maybe you need to add "groups = yes" in xinetd.conf to enable the additional groups that user amanda is in. -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Problems with amrecover in 2.4.5p1
My attempt to restore files with amrecover keep failing since I upgraded to 2.4.5. The output in amidxtaped.debug looks like: amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 20:33:06 2006 amidxtaped: version 2.4.5 amidxtaped: time 0.000: > SECURITY USER root amidxtaped: time 0.001: bsd security: remote host shannon.totalflood.com user root local user amanda amidxtaped: time 0.001: amandahosts security check passed amidxtaped: time 0.001: > CONFIG=daily1 amidxtaped: time 0.001: > LABEL=UX0027 amidxtaped: time 0.001: > FSF=18 amidxtaped: time 0.001: > HEADER amidxtaped: time 0.001: > DEVICE=/dev/ait2 amidxtaped: time 0.001: > HOST=^shannon$ amidxtaped: time 0.001: > DISK=^/var$ amidxtaped: time 0.001: > DATESTAMP=20060217 amidxtaped: time 0.001: > END amidxtaped: time 0.002: amrestore_nargs=0 amidxtaped: time 0.002: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "/dev/ait2" argv[4] = "^shannon$" argv[5] = "^/var$" argv[6] = "20060217" amrestore: could not open /dev/ait2: Permission denied amidxtaped: time 0.004: amrestore terminated normally with status: 2 amidxtaped: time 0.004: rewinding tape ... amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission denied amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006 This makes no sense to me since I was able to recover the files using amrestore on the server. The client in the above is 2.4.5p1 the server is 2.4.5 -- Stephen Carville -- polluting the ranks of skeptics since 1995. --- Government is actually the worst failure of civilized man. There has never been a really good one, and even those that are most tolerable are arbitrary, cruel, grasping and unintelligent. -- H. L. Mencken
