Re: request failed: timeout waiting for ACK
this is one of my amstatus reports: [EMAIL PROTECTED]:~/hourly$ amstatus hourly Using /usr/local/etc/amanda/hourly/amdump.1 from Thu Feb 23 10:20:59 CET 2006 pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/opt 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/usr 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/var 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) SUMMARY part real estimated size size partition : 4 estimated : 4 5154m flush : 0 0m failed : 4 5154m (100.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 0 0m 0m ( 0.00%) ( 0.00%) 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 : 0 0m 0m ( 0.00%) ( 0.00%) tape 1: 0 0m 0m ( 0.00%) hourly022 6 dumpers idle : no-dumpers taper idle network free kps: 14000 holding space :263392m (100.00%) dumper0 busy : 0:03:59 ( 40.97%) 0 dumpers busy : 0:09:45 ( 99.97%)not-idle: 0:06:15 ( 64.13%) no-bandwidth: 0:03:00 ( 30.74%) no-dumpers: 0:00:30 ( 5.12%) 1 dumper busy : 0:00:00 ( 0.00%) as you can see, amanda is doing estimates, but then doesn't do dumps. what does this error message (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) mean really ? bye Stefan Herrmann
Intelegence of amflush
Hi! It happened again, that a disk grew over the lenght of a tape, and so its backup got stuck on the holding disk. And as it is all the time it happened when i was out of office for some days... I knew its my concern as the sysadmin to split it into smaller pieces ... But it would be nice if amflush could recognise this situation and would try to flush the other backups on the holding disk if it could not flush the big one once, and not tryigng to flush the one that gave an error last time again and again producing empty tapes and ambackup fills up the holding disk with level 2 and 3 backups every night Bye, Peter WOTLmade
Re: request failed: timeout waiting for ACK
On 2006-02-23 10:45, Stefan Herrmann wrote: this is one of my amstatus reports: [EMAIL PROTECTED]:~/hourly$ amstatus hourly Using /usr/local/etc/amanda/hourly/amdump.1 from Thu Feb 23 10:20:59 CET 2006 pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/opt 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/usr 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/var 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) SUMMARY part real estimated size size partition : 4 estimated : 4 5154m flush : 0 0m failed : 4 5154m (100.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 0 0m 0m ( 0.00%) ( 0.00%) 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 : 0 0m 0m ( 0.00%) ( 0.00%) tape 1: 0 0m 0m ( 0.00%) hourly022 6 dumpers idle : no-dumpers taper idle network free kps: 14000 holding space :263392m (100.00%) dumper0 busy : 0:03:59 ( 40.97%) 0 dumpers busy : 0:09:45 ( 99.97%)not-idle: 0:06:15 ( 64.13%) no-bandwidth: 0:03:00 ( 30.74%) no-dumpers: 0:00:30 ( 5.12%) 1 dumper busy : 0:00:00 ( 0.00%) as you can see, amanda is doing estimates, but then doesn't do dumps. what does this error message (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) mean really ? Are you really really sure the estimates were done on the client,and not on the server? The server side dumper sends a request to each client, and does not receive an ACKnowkledge packet from that client within a reasonable time. I would take a look in the debug files on the client, usually in the dir /tmp/amanda/. There you can see files amandad.datetime.debug which contain the packet received, and the replies. If there are no debug files, than amandad isn't even started. Does amcheck pass all tests? -- 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: Intelegence of amflush
On 2006-02-23 11:05, Peter Mueller wrote: It happened again, that a disk grew over the lenght of a tape, and so its backup got stuck on the holding disk. And as it is all the time it happened when i was out of office for some days... I knew its my concern as the sysadmin to split it into smaller pieces ... But it would be nice if amflush could recognise this situation and would try to flush the other backups on the holding disk if it could not flush the big one once, and not tryigng to flush the one that gave an error last time again and again producing empty tapes and ambackup fills up the holding disk with level 2 and 3 backups every night What version of amanda is that? Did you specify taperalgo largestfit in the amanda.conf? Or any other? How many runtapes do you have? I guess that if you have only one runtape, and autoflush, then amanda starts a flush, while doing the estimates for the current run. It could well be that amanda does start indeed the large, probably not-fitting image (because that is the only one to choose from, even when largestfit is choosen), before the first nightly dump image is finished. In that case, it will indeed fill up the only tape. When there is only one image to choose from, Amanda will take that one, even if it will probably not fit. Changing that will make many other users of Amanda unhappy, e.g. those using hardware compression because their tape length is just a wild guess of the truth, or even me, because I underestimate the tape length a bit, so that amanda has a few percent margin with estimates being smaller than real dumps (that's why I get tapes filled with 106%). -- 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 * ***
Amdump utility still hasn't run across the firewall amcheck reports no errors.
Hi Paul again I received via the Amanda Report this morning that my server client Failed. I am still lost in the woods. On the ipchains firewall I added ipchains -M -S tcp tcpin udp to masqueraded and set the timeouts. My Amanda Report output below: server / lev 0 FAILED [Estimate timeout from server.my.co.uk] Here is my amanda client debug file It looks OK to me: amandad: debug 1 pid 4211 ruid 501 euid 501: start at Thu Feb 23 10:35:42 2006 amandad: version 2.4.4p2 amandad: build: VERSION=Amanda-2.4.4p2 amandad:BUILT_DATE=Mon Feb 20 13:24:23 GMT 2006 amandad:BUILT_MACH=Linux server 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=disk' '--with-configdir=/etc/amanda' '--with-udpportrange=1001,1009' '--with-tcpportrange=11000,11030' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ 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=enterprise 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.024: got packet: Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140687005 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.024: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 amandad: time 0.065: bsd security: remote host firewall.my.co.uk user amanda local user amanda amandad: time 0.065: amandahosts security check passed amandad: time 0.065: running service noop amandad: time 0.066: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140687005 OPTIONS features=feff9ffe0f; amandad: time 0.067: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 amandad: time 0.068: pid 4211 finish time Thu Feb 23 10:35:42 2006 Cheers -- 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
Re: Amdump utility still hasn't run across the firewall amcheck reports no errors.
On 2006-02-23 11:36, Chuck Amadi Systems Administrator wrote: Hi Paul again I received via the Amanda Report this morning that my server client Failed. I am still lost in the woods. On the ipchains firewall I added ipchains -M -S tcp tcpin udp to masqueraded and set the timeouts. My Amanda Report output below: server / lev 0 FAILED [Estimate timeout from server.my.co.uk] Here is my amanda client debug file It looks OK to me: There should be more debug files. This is the succeeded noop request (for the exchange of the features between client and host). There should also be a sendsize request in another amanda.*.debug file. That one should contain timestamps. Verify if the ACK is sent within the udp timeout from ipchains. Do you see that UDP packet logged in the firewall logs? amandad: time 0.024: got packet: Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140687005 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; The text between the hyhens is the REQuest packet and you see the line SERVICE noop. amandad: time 0.024: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 ANd this is the ACK package, sent back immediatly (without the millisecond). amandad: time 0.065: bsd security: remote host firewall.my.co.uk user amanda local user amanda amandad: time 0.065: amandahosts security check passed amandad: time 0.065: running service noop amandad: time 0.066: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140687005 OPTIONS features=feff9ffe0f; And here is the reply package, 0.021 seconds later. amandad: time 0.067: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 And an ACK from the server indicating good delivery over there. amandad: time 0.068: pid 4211 finish time Thu Feb 23 10:35:42 2006 And all this took only 0.068 seconds. Now find the amanda.*.debug file for the SERVICE sendsize, and look for the timestamps. Find out where the connection is lost. -- 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: Amdump utility still hasn't run across the firewall amcheck reports no errors.
Hi Here is my sendsize log. sendsize[2481]: time 220.652: Total bytes written: 5132001280 (4.8GB, 22MB/s) sendsize[2481]: time 220.726: . sendsize[2481]: estimate time for / level 0: 220.672 sendsize[2481]: estimate size for / level 0: 5011720 KB sendsize[2481]: time 220.727: waiting for /bin/tar / child sendsize[2481]: time 220.727: after /bin/tar / wait sendsize[2481]: time 220.736: done with amname '/', dirname '/', spindle -1 sendsize[2479]: time 220.822: child 2481 terminated normally sendsize: time 220.823: pid 2479 finish time Wed Feb 22 21:04:3 On the firewall run less /var/log/messages and search for udp and port 1001 and 1009 no UDP Packets log entries unless I need to search for something else. Cheers On Thu, 2006-02-23 at 11:42 +0100, Paul Bijnens wrote: On 2006-02-23 11:36, Chuck Amadi Systems Administrator wrote: Hi Paul again I received via the Amanda Report this morning that my server client Failed. I am still lost in the woods. On the ipchains firewall I added ipchains -M -S tcp tcpin udp to masqueraded and set the timeouts. My Amanda Report output below: server / lev 0 FAILED [Estimate timeout from server.my.co.uk] Here is my amanda client debug file It looks OK to me: There should be more debug files. This is the succeeded noop request (for the exchange of the features between client and host). There should also be a sendsize request in another amanda.*.debug file. That one should contain timestamps. Verify if the ACK is sent within the udp timeout from ipchains. Do you see that UDP packet logged in the firewall logs? amandad: time 0.024: got packet: Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140687005 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; The text between the hyhens is the REQuest packet and you see the line SERVICE noop. amandad: time 0.024: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 ANd this is the ACK package, sent back immediatly (without the millisecond). amandad: time 0.065: bsd security: remote host firewall.my.co.uk user amanda local user amanda amandad: time 0.065: amandahosts security check passed amandad: time 0.065: running service noop amandad: time 0.066: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140687005 OPTIONS features=feff9ffe0f; And here is the reply package, 0.021 seconds later. amandad: time 0.067: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 And an ACK from the server indicating good delivery over there. amandad: time 0.068: pid 4211 finish time Thu Feb 23 10:35:42 2006 And all this took only 0.068 seconds. Now find the amanda.*.debug file for the SERVICE sendsize, and look for the timestamps. Find out where the connection is lost. -- 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
Slow dump of small directory...
Any idea why I get the following? fileserv:/usr/freeware/etc/openldap 1 32k dumping0k ( 1.53%) (11:32:10) This is from amstatus on a currently running dump, and the time is now # date Thu Feb 23 12:32:35 CET 2006 I mean, why does this dump take so long? This is (as you can see) a level 1 dump. I don't think anything at all has changed since the last level 0. The total size of the directory is only 544k. Amanda version 2.4.4p3. - Toralf
Re: Slow dump of small directory...
Toralf Lund wrote: Any idea why I get the following? fileserv:/usr/freeware/etc/openldap 1 32k dumping0k ( 1.53%) (11:32:10) This is from amstatus on a currently running dump, and the time is now # date Thu Feb 23 12:32:35 CET 2006 I mean, why does this dump take so long? I get these very often. Your dump isn't really taking so long, in fact it's been finished for quite some time. For tiny (essentially empty) dumps, amstatus sometimes doesn't seem to notice them being finished. I haven't investigated any further. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: Slow dump of small directory...
Any idea why I get the following? fileserv:/usr/freeware/etc/openldap 1 32k dumping0k ( 1.53%) (11:32:10) This is from amstatus on a currently running dump, and the time is now # date Thu Feb 23 12:32:35 CET 2006 I mean, why does this dump take so long? I get these very often. Yeah, me to. I meant to say, this (i.e. a *long* time apparently spent on small dumps) is the normal situation - not something exceptional I'm seeing right now. Your dump isn't really taking so long, in fact it's been finished for quite some time. For tiny (essentially empty) dumps, amstatus sometimes doesn't seem to notice them being finished. I haven't investigated any further. Right... What's strange, though, is that the amdump as been busy for *hours* working only on a relatively small number of tiny dumps (I mean, after some other, larger dumps were done.) So, doesn't amdump itself notice that they are finished, either? Or should I expect that the incremental dump takes long even though it is empty, when the directory itself (or size of a full dump, if you like) is very large? I mean, the directory I mentioned does not contain a lot of data, but some of the others being busy dumping for a long time hold several gigabytes, but also have no updated files. - Toralf
Re: Intelegence of amflush
Hi again! Did you specify taperalgo largestfit in the amanda.conf? Or any other? I will check that, probably not, because I dont remember this parameter. Is was missing, which means first - I changed this to smallest to give the 2rd and 3rd level images a chance to get thru .. I taped the too big image by hand. But now I am stuck with a question I didnt get an answer when I posted it here last time: What's the correct way to remove an image from the holding disk, that cant be backed up by using amflush (because its too big !?!): -) Is it sufficcient to remove it by unix rm ? -) Is there any command e.g. with amadmin to remove it -) Is there any way to tell amanda that this image does not exist, or that its' backed up (by hand to tapes not labeled by amanda in my case) ? Maybe one of the amanda gurus could give me the pointer where in the docs this is discussed Bye, Peter WOTLmade
Re: request failed: timeout waiting for ACK
Am 23.02.2006 um 11:17 schrieb Paul Bijnens: On 2006-02-23 10:45, Stefan Herrmann wrote: this is one of my amstatus reports: [EMAIL PROTECTED]:~/hourly$ amstatus hourly Using /usr/local/etc/amanda/hourly/amdump.1 from Thu Feb 23 10:20:59 CET 2006 pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/opt 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/usr 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/var 1 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) SUMMARY part real estimated size size partition : 4 estimated : 4 5154m flush : 0 0m failed : 4 5154m (100.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 0 0m 0m ( 0.00%) ( 0.00%) 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 : 0 0m 0m ( 0.00%) ( 0.00%) tape 1: 0 0m 0m ( 0.00%) hourly022 6 dumpers idle : no-dumpers taper idle network free kps: 14000 holding space :263392m (100.00%) dumper0 busy : 0:03:59 ( 40.97%) 0 dumpers busy : 0:09:45 ( 99.97%)not-idle: 0:06:15 ( 64.13%) no-bandwidth: 0:03:00 ( 30.74%) no-dumpers: 0:00:30 ( 5.12%) 1 dumper busy : 0:00:00 ( 0.00%) as you can see, amanda is doing estimates, but then doesn't do dumps. what does this error message (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) mean really ? Are you really really sure the estimates were done on the client,and not on the server? yes i am, i saw the processes running on the client. The server side dumper sends a request to each client, and does not receive an ACKnowkledge packet from that client within a reasonable time. ok thanks for the explanation. I would take a look in the debug files on the client, usually in the dir /tmp/amanda/. There you can see files amandad.datetime.debug which contain the packet received, and the replies. If there are no debug files, than amandad isn't even started. amandad: debug 1 pid 20533 ruid 2 euid 2: start at Thu Feb 23 14:19:14 2006 amandad: version 2.4.5 amandad: build: VERSION=Amanda-2.4.5 amandad:BUILT_DATE=Thu Feb 23 10:10:42 CET 2006 amandad:BUILT_MACH=FreeBSD pille.hq.imos.net 5.4-RELEASE-p3 FreeBSD 5.4-RELEASE-p3 #0: Sat Jul 2 16:02:43 CEST 2005 [...] amandad: time 30.002: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.002: error receiving message: timeout amandad: time 30.002: pid 20533 finish time Thu Feb 23 14:19:44 2006 Does amcheck pass all tests? yes: [EMAIL PROTECTED]:~$ amcheck hourly Amanda Tape Server Host Check - Holding disk /holding: 264416 MB disk space available, using 263392 MB read label `hourly023', date `20060223' read label `hourly024', date `X' NOTE: skipping tape-writable test Tape hourly024 label ok NOTE: info dir /usr/local/etc/amanda/hourly/curinfo/pille.hq.imos.net/_: does not exist NOTE: it will be created on the next run. Server check took 0.167 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.868 seconds, 0 problems found (brought to you by Amanda 2.5.0b2) bye Stefan Herrmann
Re: Intelegence of amflush
On 2006-02-23 14:03, Peter Mueller wrote: Paul Bijnens wrote: When there is only one image to choose from, Amanda will take that one, even if it will probably not fit. Changing that will make many other users of Amanda unhappy, e.g. those using hardware compression because their tape length is just a wild guess of the truth, or even me, because I underestimate the tape length a bit, so that amanda has a few percent margin with estimates being smaller than real dumps (that's why I get tapes filled with 106%). That's perfectly o.k. . But im my case there where about 25 images to choose from. But it will choose the correct one when you specify taperalgo largestfit. (The default is the first one found.) I was thinking about an error recovery strategy by remembering that this image introduced an error last time, so if there are several others, skip it first and give the others a try so that they get a chance to find their way to the tape The problem here is that when you had a real tape error, and then try to flush o a new tape, then amanda refuses to put that one tape, because it got an error last time? Not good. So how you do see if you got a real error or just EOT. Explain me, because I surely want to know. AFAICT most drivers do not distinguish between write error or EOT. (At least that is my experience.) But anyway, I have allready changed the disklist so hopefully in two or three days the new split up disks will be backed up until it strikes next time. See also: http://wiki.zmanda.com/index.php/Filling_a_tape_to_100%25 -- 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: Intelegence of amflush
On 2006-02-23 14:18, Peter Mueller wrote: Did you specify taperalgo largestfit in the amanda.conf? Or any other? I will check that, probably not, because I dont remember this parameter. Is was missing, which means first - I changed this to smallest to give the 2rd and 3rd level images a chance to get thru .. The largestfit reverts to smallest when nothing fits (because that one has the most chance of fitting in the unknown gap near the end of tape). When start taping smallest in the beginning, you got only large ones left near the end of a tape, and that means you loose a lot of the tape capacity, because the failed image has to be started all over again on the next tape. But now I am stuck with a question I didnt get an answer when I posted it here last time: What's the correct way to remove an image from the holding disk, that cant be backed up by using amflush (because its too big !?!): -) Is it sufficcient to remove it by unix rm ? yes. and in that case you better schedule a level 0 again for that DLE. -) Is there any command e.g. with amadmin to remove it no, but it would be a nice addition. -) Is there any way to tell amanda that this image does not exist, or that its' backed up (by hand to tapes not labeled by amanda in my case) ? no. but would be nice. -- 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: Intelegence of amflush
On Thu, Feb 23, 2006 at 02:31:06PM +0100, Paul Bijnens enlightened us: Paul Bijnens wrote: When there is only one image to choose from, Amanda will take that one, even if it will probably not fit. Changing that will make many other users of Amanda unhappy, e.g. those using hardware compression because their tape length is just a wild guess of the truth, or even me, because I underestimate the tape length a bit, so that amanda has a few percent margin with estimates being smaller than real dumps (that's why I get tapes filled with 106%). That's perfectly o.k. . But im my case there where about 25 images to choose from. But it will choose the correct one when you specify taperalgo largestfit. (The default is the first one found.) At least with 2.4.5, largestfit means of the oldest date, the largest that will fit. If you have 20GB tapes and a dump on Feb 15th that is 23GB and a dump on Feb 16th that is 13GB, it will pick the Feb 15th because it is older. Has this been changed in 2.5? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: request failed: timeout waiting for ACK
On 2006-02-23 14:24, Stefan Herrmann wrote: Am 23.02.2006 um 11:17 schrieb Paul Bijnens: I would take a look in the debug files on the client, usually in the dir /tmp/amanda/. There you can see files amandad.datetime.debug which contain the packet received, and the replies. If there are no debug files, than amandad isn't even started. amandad: debug 1 pid 20533 ruid 2 euid 2: start at Thu Feb 23 14:19:14 2006 amandad: version 2.4.5 amandad: build: VERSION=Amanda-2.4.5 amandad:BUILT_DATE=Thu Feb 23 10:10:42 CET 2006 amandad:BUILT_MACH=FreeBSD pille.hq.imos.net 5.4-RELEASE-p3 FreeBSD 5.4-RELEASE-p3 #0: Sat Jul 2 16:02:43 CEST 2005 [...] amandad: time 30.002: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.002: error receiving message: timeout amandad: time 30.002: pid 20533 finish time Thu Feb 23 14:19:44 2006 You left out just the useful information. Or the fact that there is none. From the above, it seems like there was no REQ packet at all. You get that also when you portscan the client, and tickle the (x)inetd daemon that a new packet is received on port 10080. Or when you start amandad manually. In that case, amandad waits for a UDP packet, and times out after 30 seconds. So, question is: is there a UDP packet (invalid, corrupt...) in the lines that you cut out? -- 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
Am 23.02.2006 um 14:43 schrieb Paul Bijnens: On 2006-02-23 14:24, Stefan Herrmann wrote: Am 23.02.2006 um 11:17 schrieb Paul Bijnens: I would take a look in the debug files on the client, usually in the dir /tmp/amanda/. There you can see files amandad.datetime.debug which contain the packet received, and the replies. If there are no debug files, than amandad isn't even started. amandad: debug 1 pid 20533 ruid 2 euid 2: start at Thu Feb 23 14:19:14 2006 amandad: version 2.4.5 amandad: build: VERSION=Amanda-2.4.5 amandad:BUILT_DATE=Thu Feb 23 10:10:42 CET 2006 amandad:BUILT_MACH=FreeBSD pille.hq.imos.net 5.4-RELEASE-p3 FreeBSD 5.4-RELEASE-p3 #0: Sat Jul 2 16:02:43 CEST 2005 [...] amandad: time 30.002: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.002: error receiving message: timeout amandad: time 30.002: pid 20533 finish time Thu Feb 23 14:19:44 2006 You left out just the useful information. Or the fact that there is none. From the above, it seems like there was no REQ packet at all. You get that also when you portscan the client, and tickle the (x)inetd daemon that a new packet is received on port 10080. Or when you start amandad manually. In that case, amandad waits for a UDP packet, and times out after 30 seconds. So, question is: is there a UDP packet (invalid, corrupt...) in the lines that you cut out? i think there was no useful information in the leftout part, but look for yourself: amandad: debug 1 pid 20420 ruid 2 euid 2: start at Thu Feb 23 14:19:12 2006 amandad: version 2.4.5 amandad: build: VERSION=Amanda-2.4.5 amandad:BUILT_DATE=Thu Feb 23 10:10:42 CET 2006 amandad:BUILT_MACH=FreeBSD pille.hq.imos.net 5.4-RELEASE-p3 FreeBSD 5.4-RELEASE-p3 #0: Sat Jul 2 16:02:43 CEST 2005 [EMAIL PROTECTED]:/usr /obj/usr/src/sys/IMOS i386 amandad:CC=cc amandad:CONFIGURE_COMMAND='./configure' '--libexecdir=/usr/local/libexec/amanda' '--with-amandahosts' '--with-fqdn' '--with-dump-honor-nodump' '--with-buffered-dump' '--without-server' '--disable-libtool' '--prefix=/usr/local' '--with-user=operator' '--with-group=operator' '--with-gnutar-listdi r=/usr/local/var/amanda/gnutar-lists' '--with-gnutar=/usr/local/bin/gtar' '--with-index-server=amanda.hq.imos.net' '--with-tape-server=amanda.hq.imos.ne t' '--with-config=hourly' '--prefix=/usr/local' '--build=i386-portbld-freebsd5.4' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec/amanda amandad:mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda amandad:AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/local/bin/smbclient amandad:GNUTAR=/usr/local/bin/gtar 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=amanda.hq.imos.net amandad:DEFAULT_CONFIG=hourly amandad:DEFAULT_TAPE_SERVER=amanda.hq.imos.net amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL DEBUG_CODE AMANDA_DEBUG_DAYS=4 amandad:BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=operator amandad:FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz amandad:COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best amandad:UNCOMPRESS_OPT=-dc amandad: time 30.006: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.006: error receiving message: timeout amandad: time 30.006: pid 20420 finish time Thu Feb 23 14:19:42 2006 bye Stefan Herrmann
Re: Intelegence of amflush
Hi Paul! Paul Bijnens wrote: On 2006-02-23 14:18, Peter Mueller wrote: Did you specify taperalgo largestfit in the amanda.conf? Or any other? I will check that, probably not, because I dont remember this parameter. Is was missing, which means first - I changed this to smallest to give the 2rd and 3rd level images a chance to get thru .. The largestfit reverts to smallest when nothing fits (because that one has the most chance of fitting in the unknown gap near the end of tape). When start taping smallest in the beginning, you got only large ones left near the end of a tape, and that means you loose a lot of the tape capacity, because the failed image has to be started all over again on the next tape. O.k. I will try largestfit, but in normal situations all my dumps fit on one tape anyway, as my setup is rather simple, without changer and optimised to use this one tape each night ... Normally I tend to split up disks so that they are definitely smaller than the tape ... but if Users change usage policy without noticing me - it fails ... But now I am stuck with a question I didnt get an answer when I posted it here last time: What's the correct way to remove an image from the holding disk, that cant be backed up by using amflush (because its too big !?!): -) Is it sufficcient to remove it by unix rm ? yes. and in that case you better schedule a level 0 again for that DLE. -) Is there any command e.g. with amadmin to remove it no, but it would be a nice addition. -) Is there any way to tell amanda that this image does not exist, or that its' backed up (by hand to tapes not labeled by amanda in my case) ? no. but would be nice. Thanks! Bye, Peter WOTLmade
Re: request failed: timeout waiting for ACK
On 2006-02-23 15:54, Stefan Herrmann wrote: i think there was no useful information in the leftout part, but look for yourself: Yes indeed. No REQ packet at all. Are you sure this debug file is the result from a amdump request, and not one of those that were generated by all different commands to solve this strange problem? e.g. starting amandad from the command line, gives exactly the same output. Are the datestamps consistent with the amdump.1 file? Another thing to use a network packet dumper to see if the packet got dropped/lost somewhere. Both on the server and the client, and verify if the client receives what the server sends. tcpdump -X -s 1500 udp and port 10080 should work. -- 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: Intelegence of amflush
Hi Paul! Paul Bijnens wrote: ... The problem here is that when you had a real tape error, and then try to flush o a new tape, then amanda refuses to put that one tape, because it got an error last time? Not good. So how you do see if you got a real error or just EOT. Explain me, because I surely want to know. AFAICT most drivers do not distinguish between write error or EOT. (At least that is my experience.) I think we discussed the EOT versus real tape error here some weeks ago ... O.k. maybe I expect a little to much guessing - my thought was, that the image that failed last time gets sheduled at the end, not recoginsed in the choosing and ordering process for each flush, so if the flush is done, the others have there chance. If a tape error was the reason why the flush failed, the following run - expecting the next tape is o.k. - will work anyway, anly the order of the images on tape is changed. But if the image was the reason why the flush failed, all the other images may move to tape, and the error on will propably trigger its error again. Size may not be the only reason why the image failes to tape - there may be a hardware error e.g. disk or controller which prevents it from taping - would be a bad thing anyway - but especially in such situations it would be fine if at least the rest is taped. Another problem in the flush stategy is mentioned in a reply of Matt Hyclak: The top level criteria for ordering the images to flush seems to be the date. As in my case, where one big image left over from a ambackup run, all following ambackup runs produce 2rd and 3rd level backups to fit into the remaining holding disk. The flush runs, either triggered by ambackup or manually continue to try the one big image becaus its from an older ambackup run Bye, Peter WOTLmade
Still: Problems with amrestore - please HELP - stderr output
When I run amrestore like this amrestore -f 0 -p /dev/nst0 localhost sda2 | restore -ivb2 -f - I got message: Verify tape and initialize maps Input is from a local file/pipe amrestore: 0: skipping start of tape: date 20060223 label EPIP2 amrestore: 1: restoring localhost.sda2.20060223.0 restore: Tape is not a dump tape Error 32 (Broken pipe) offset 1024+1024, wrote 0 amrestore: pipe reader has quit in middle of file. Of course I CAN RESTORE it on production server where it was backed up ! ? Please advice ... I'm loosing faith in my self and open source ;-) Kevin Till [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2006-02-22 00:57 To Radek Cisz [EMAIL PROTECTED] cc amanda-users@amanda.org Subject 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
amandad can't be started
Dear group, i´am trying to install the amanda client from the current version. I´ve configured it with user=amanda group=disk and client installation only The prefix is /usr/amanda. The problem is, that the amandad can´t be started. I execute $Prefix/libexec/amandad, this takes a while (30 secs) and breaks. The Logfile says: serv:/usr/amanda/libexec# cat /tmp/amanda/amandad.20060220015348.debug amandad: debug 1 pid 2500 ruid 1000 euid 1000: start at Mon Feb 20 01:53:48 2006 amandad: version 2.4.5p1 snip Building Infos /snip amandad: time 29.992: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.993: error receiving message: timeout amandad: time 29.993: pid 2500 finish time Mon Feb 20 01:54:18 2006 This is my inetd.conf: serv:/usr/amanda# cat /etc/inetd.conf # /etc/inetd.conf: see inetd(8) for further informations. # # Internet server configuration database # # # Lines starting with #:LABEL: or #off# should not # be changed unless you know what you are doing! # # If you want to disable an entry so it isn't touched during # package updates just comment it out with a single '#' character. # # Packages should modify this file by using update-inetd(8) # # service_name sock_type proto flags user server_path args # #:INTERNAL: Internal services #echo stream tcp nowait root internal #echo dgram udp wait root internal #chargen stream tcp nowait root internal #chargen dgram udp wait root internal #discard stream tcp nowait root internal #discard dgram udp wait root internal #daytime stream tcp nowait root internal #daytime dgram udp wait root internal #time stream tcp nowait root internal #time dgram udp wait root internal #:STANDARD: These are standard services. #:BSD: Shell, login, exec and talk are BSD protocols. shell stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.rshd login stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.rlogind exec stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.rexecd amanda dgram udp wait amanda /usr/amanda/libexec/amandad amandad The /etc/services file: hitchhiker:/usr/amanda/libexec# cat /etc/services | grep amanda amanda 10080/udp # Amanda backup services kamanda 10081/tcp # amanda backup services (Kerberos) kamanda 10081/udp amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services The inetd seems to work: serv:/usr/amanda/libexec# netstat -a | grep amanda udp 0 0 *:amanda *:* The /etc/hosts.deny and /etc/hosts.allow files are empty. The Items in http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out seems to be correct. Any suggestions? Greetings, Patrick
Re: Still: Problems with amrestore - please HELP - stderr output
Its dump archive. please see my first letter below Regards: 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??? -- Paul Bijnens [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2006-02-23 16:24 To Radek Cisz [EMAIL PROTECTED] cc amanda-users@amanda.org Subject Re: Still: Problems with amrestore - please HELP - stderr output On 2006-02-23 16:19, Radek Cisz wrote: When I run amrestore like this amrestore -f 0 -p /dev/nst0 localhost sda2 | restore -ivb2 -f - I got message: Verify tape and initialize maps Input is from a local file/pipe amrestore: 0: skipping start of tape: date 20060223 label EPIP2 amrestore: 1: restoring localhost.sda2.20060223.0 restore: Tape is not a dump tape Is it a dump image or is it gnutar image? Error 32 (Broken pipe) offset 1024+1024, wrote 0 amrestore: pipe reader has quit in middle of file. Of course I CAN RESTORE it on production server where it was backed up ! ? Please advice ... I'm loosing faith in my self and open source ;-) There is no substitute for learning. But for Open Source software at least you're not bound by the details that the vendor publishes. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +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: Still: Problems with amrestore - please HELP - stderr output
On 2006-02-23 16:30, Radek Cisz wrote: Its dump archive. please see my first letter below OK. Then maybe you have some difference in blocksize between the two machines. Some implemenations (HPUX in my experience) read a block, and if the tapeblocksize is greater than the readblocksize, then they throw away the excessive bytes. Is Suse9 like that too? Easy to find out: restore the image to disk, and verify the size. or use dd ibs=256k if=/dev/nst0 of=outfile (a very large blocksize and explicitly say ibs instead of bs) and verify if the files on both systems are at least the same size, and moreover the same md5 checksum. On these servers I have installed Suse 9.0 and amanda from rpm package. Is the other server a different OS version? -- 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
On Thu, Feb 23, 2006 at 02:24:59PM +0100, Stefan Herrmann wrote: Does amcheck pass all tests? yes: [EMAIL PROTECTED]:~$ amcheck hourly Amanda Tape Server Host Check A config named hourly. Do you actually run amdump each hour? If so, might there be some extraneous, old, stuck, ??? amanda processes still running 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: Still: Problems with amrestore - please HELP - stderr output
Radek Cisz wrote: When I run amrestore like this amrestore -f 0 -p /dev/nst0 localhost sda2 | restore -ivb2 -f - I got message: Verify tape and initialize maps Input is from a local file/pipe amrestore: 0: skipping start of tape: date 20060223 label EPIP2 amrestore: 1: restoring localhost.sda2.20060223.0 restore: Tape is not a dump tape Error 32 (Broken pipe) offset 1024+1024, wrote 0 amrestore: pipe reader has quit in middle of file. Of course I CAN RESTORE it on production server where it was backed up ! ? wait, amrestore does not go across the network to the server to retrieve image. (Amrecover will.) Amrestore extracts backup images from the tape mounted on tapedevice or from the holding disk file -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: encryption with 2.5.0b2
On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote: - What is the point to uuencode and encrypt (with gpg) random data to generate the key? Since the passphrase is stored on the same host, protecting the key with the passprase is not of much use (IMHO). It illustrates the method of using multi-key which a strong point of aespipe. OK, I see. multi-key was the magic word that (after some googling) made me understand what's going on here. AFAICS, multi-keys can prevent watermark-attacks? Are there more advantages to them? And it's a symmetric encryption and to facilitate automatic backup, the passphrase has to be stored somewhere. This is (one) of the reasons why I'd prefer a pubkey method: You don't have the passphrase lying around on a networked box. - Why using aespipe at all? Is there any reason not to use gpg? AFAICS, aespipe introduces only an additinal layer of complexity. Amanda users have used aespipe in the past, so it's there. Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated because the kernel developers want to switch to devmapper. Please correct me and clarify if I'm wrong. I believe aespipe gives better performance since gpg is doing more than just encryption. AFAIK, gpg does compression in addition to encryption. But then you need to compare gzip+aespipe against gpg. Or did you mean something different? - Since the server says whether/which encryption is to be used, the server can request unencrypted backups from the client. This implies that the server has to be trusted. Use auth ssh/krb4/krb5 to enable transport encryption. I am not about transport encryption here. I am about not trusting the amanda server. Thanks for the explanations, Kevin!
Re: amandad can't be started
On Thu, Feb 23, 2006 at 04:34:19PM +0100, Patrick Mania wrote:
Dear group,
The problem is, that the amandad canŽt be started.
I execute $Prefix/libexec/amandad, this takes a while (30 secs) and breaks.
amandad is not intended to run continually nor to be run from the command line.
It starts as needed by {x}inetd and communicates over the network.
You are just seeing its timeout and exit when no one is talking to it
over the network.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amandad can't be started
Jon LaBadie wrote:
On Thu, Feb 23, 2006 at 04:34:19PM +0100, Patrick Mania wrote:
Dear group,
The problem is, that the amandad canŽt be started.
I execute $Prefix/libexec/amandad, this takes a while (30 secs) and breaks.
amandad is not intended to run continually nor to be run from the command line.
It starts as needed by {x}inetd and communicates over the network.
You are just seeing its timeout and exit when no one is talking to it
over the network.
Hi Jon,
thanks for your reply. I´ve just started the amandad manually because on
amcheck from the amanda server the result is request timed out for
this machine.
Greetings,
Patrick
Host down message on localhost client
Hello,I am attempting to get the functionality of AMANDA down and during the initial testing locally. I am discarding tape data by putting 'tapedev "null:" ' in amanda.conf. When I run amcheck, I receive the a "host down" message even though my backup backup client is on the same host as server, my system is a solaris 10: [host] ~ amcheck ProtoLocalAmanda Tape Server Host Check-WARNING: tapedev is null:, dumps will be thrown awayHolding disk /amanda-vtapes-local/ProtoLocal: 9375682 KB disk space available, that's plentyNOTE: skipping tape checksNOTE: info dir /usr/adm/amanda/ProtoLocal/curinfo: does not existNOTE: it will be created on the next runServer check took 0.002 seconds Amanda Backup Client Hosts CheckWARNING: localhost: selfcheck request timed out.! ; Host down?Client check: 1 host checked in 30.027 seconds, 1 problem found (brought to you by Amanda 2.4.4)__My log file reads:[host] /usr/adm/amanda/ProtoLocal more log.20060223.0START driver date 20060223DISK planner localhost /itrn1START planner date 20060223INFO planner Adding new disk localhost:/itrn1.START taper datestamp 20060223 label [fake-label] tape 0WARNING taper tapedev is null:, dumps will be thrown awayERROR planner Request to localhost timed out.FINISH planner date 20060223WARNING driver WARNING: got empty schedule from plannerSTATS driver startup time 30.035INFO taper tape [fake-label] kb 0 fm 0 [OK]FINISH driver date 20060223 time 30.055 A portion of my dump.1 reads: [host] /usr/adm/amanda/ProtoLocal more amdump.1 . . . GETTING ESTIMATES...driver: started dumper0 pid 1632driver: started dumper1 pid 1633driver: started dumper2 pid 1634driver: started dumper3 pid 1635taper: pid 1631 executable taper version 2.4.4dumper: dgram_bind: socket bound to 0.0.0.0.753dumper: pid 1632 executable dumper0 version 2.4.4, using port 753taper: page size is 8192taper: buffer size is 32768dumper: dgram_bind: socket bound to 0.0.0.0.754dumper: pid 1633 executable dumper1 version 2.4.4, using port 754dumper: dgram_bind: socket bound to 0.0.0.0.755 ___/etc/services reads:#amandaamanda 10080/udpamandaidx 10082/tcpamidxtape 10083/tcp /etc/inetd.conf#amandaamanda dgram udp wait amanda /opt/sfw/libexec/amandad amandadamandaidx stream tcp nowait amanda /opt/sfw/libexec/amindexd amindexdamidxtape stream tcp nowait amanda /opt/sfw/libexec/amidxtaped amidxtaped -- Yahoo! Mail Use Photomail to share photos without annoying attachments.
Re: Host down message on localhost client
On Thu, Feb 23, 2006 at 03:11:47PM -0800, Wayne Thorpe wrote: Hello, I am attempting to get the functionality of AMANDA down and during the initial testing locally. I am discarding tape data by putting 'tapedev null: ' in amanda.conf. When I run amcheck, I receive the a host down message even though my backup backup client is on the same host as server, my system is a solaris 10: [host] ~ amcheck ProtoLocal Amanda Tape Server Host Check - WARNING: tapedev is null:, dumps will be thrown away Holding disk /amanda-vtapes-local/ProtoLocal: 9375682 KB disk space available, that's plenty NOTE: skipping tape checks NOTE: info dir /usr/adm/amanda/ProtoLocal/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.002 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.027 seconds, 1 problem found (brought to you by Amanda 2.4.4) __ My log file reads: [host] /usr/adm/amanda/ProtoLocal more log.20060223.0 START driver date 20060223 DISK planner localhost /itrn1 START planner date 20060223 INFO planner Adding new disk localhost:/itrn1. START taper datestamp 20060223 label [fake-label] tape 0 WARNING taper tapedev is null:, dumps will be thrown away ERROR planner Request to localhost timed out. FINISH planner date 20060223 WARNING driver WARNING: got empty schedule from planner STATS driver startup time 30.035 INFO taper tape [fake-label] kb 0 fm 0 [OK] FINISH driver date 20060223 time 30.055 A portion of my dump.1 reads: [host] /usr/adm/amanda/ProtoLocal more amdump.1 . . . GETTING ESTIMATES... driver: started dumper0 pid 1632 driver: started dumper1 pid 1633 driver: started dumper2 pid 1634 driver: started dumper3 pid 1635 taper: pid 1631 executable taper version 2.4.4 dumper: dgram_bind: socket bound to 0.0.0.0.753 dumper: pid 1632 executable dumper0 version 2.4.4, using port 753 taper: page size is 8192 taper: buffer size is 32768 dumper: dgram_bind: socket bound to 0.0.0.0.754 dumper: pid 1633 executable dumper1 version 2.4.4, using port 754 dumper: dgram_bind: socket bound to 0.0.0.0.755 ___ /etc/services reads: #amanda amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp /etc/inetd.conf #amanda amanda dgram udp wait amanda /opt/sfw/libexec/amandad amandad amandaidx stream tcp nowait amanda /opt/sfw/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /opt/sfw/libexec/amidxtaped amidxtaped -- Doesn't matter that server and client are same computer. Still needs all the same setup as a remote client. Try HARD to not use localhost use a valid hostname. Thar be snakes in them thar waters Solaris 10, have you used ?inetconv? to switch the amanda service over to smf? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: encryption with 2.5.0b2
Josef Wolf wrote: On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote: - What is the point to uuencode and encrypt (with gpg) random data to generate the key? Since the passphrase is stored on the same host, protecting the key with the passprase is not of much use (IMHO). It illustrates the method of using multi-key which a strong point of aespipe. OK, I see. multi-key was the magic word that (after some googling) made me understand what's going on here. AFAICS, multi-keys can prevent watermark-attacks? Are there more advantages to them? basically to make dictionary attack almost impossible given that the passphrase is not in the wrong hand. And it's a symmetric encryption and to facilitate automatic backup, the passphrase has to be stored somewhere. This is (one) of the reasons why I'd prefer a pubkey method: You don't have the passphrase lying around on a networked box. Yes. Keep in mind that the passphrase (be it in symmetric or public-key encryption cases) still need to be properly stored and managed. I know, you can store the private-key of the public-key method offline and only use it for backup recover. - Why using aespipe at all? Is there any reason not to use gpg? AFAICS, aespipe introduces only an additinal layer of complexity. Amanda users have used aespipe in the past, so it's there. Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated because the kernel developers want to switch to devmapper. Please correct me and clarify if I'm wrong. devmapper seems to be merged into the mainline Linux and loop-aes has not. However, for the purpose of backup encryption, it's still a valid solution. Debian and Gentoo distribute it and it's actively maintained by the author. I believe aespipe gives better performance since gpg is doing more than just encryption. AFAIK, gpg does compression in addition to encryption. But then you need to compare gzip+aespipe against gpg. Or did you mean something different? gpg also does mdc (modification detection code). - Since the server says whether/which encryption is to be used, the server can request unencrypted backups from the client. This implies that the server has to be trusted. Use auth ssh/krb4/krb5 to enable transport encryption. I am not about transport encryption here. I am about not trusting the amanda server. That's how ssh will help here. When server starts the process(/usr/bin/ssh -l amandabackup ../amandad) on the client. The client sshd will perform RSA based authentication on the server. It improves security. What if the server is totally compromised? It's time to look at SELinux(Redhat) and or AppArmor(SuSE) -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: encryption with 2.5.0b2
On Thu, Feb 23, 2006 at 03:50:11PM -0800, Kevin Till wrote: Josef Wolf wrote: On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote: Amanda users have used aespipe in the past, so it's there. Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated because the kernel developers want to switch to devmapper. Please correct me and clarify if I'm wrong. devmapper seems to be merged into the mainline Linux and loop-aes has not. However, for the purpose of backup encryption, it's still a valid solution. Debian and Gentoo distribute it and it's actively maintained by the author. devmapper/loop-aes/aespipe, all linux'isms ?? And some as kernel facilities? How do they fit with compiling amanda on unix, various BSDs, Solaris, AIX, Tru64, HP-UX, OSX, and/or cygwin? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: encryption with 2.5.0b2
Jon LaBadie wrote: On Thu, Feb 23, 2006 at 03:50:11PM -0800, Kevin Till wrote: Josef Wolf wrote: On Wed, Feb 22, 2006 at 03:34:44PM -0800, Kevin Till wrote: Amanda users have used aespipe in the past, so it's there. Hmmm, AFAIK is aespipe part of loop-aes and loop-aes is deprecated because the kernel developers want to switch to devmapper. Please correct me and clarify if I'm wrong. devmapper seems to be merged into the mainline Linux and loop-aes has not. However, for the purpose of backup encryption, it's still a valid solution. Debian and Gentoo distribute it and it's actively maintained by the author. devmapper/loop-aes/aespipe, all linux'isms ?? And some as kernel facilities? How do they fit with compiling amanda on unix, various BSDs, Solaris, AIX, Tru64, HP-UX, OSX, and/or cygwin? no problem. Encryption is an optional dumptype feature. Only the hooks which make no specific assumption on what kind of encryption are compiled in. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Problems building 2.5 B2
I'm trying to compile 2.5 beta 2 on Solaris 10 X86. The build is failing in the man subdirectory. It's complaining about this line in the generated Makefile: $(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl $(XSLTPROC) --path xslt/ --output $@ man.xsl $ Now, it's been a while since I wrote Makefiles, but I must admit that I don't undrstand rh %: myself. Anyone know what's _suuposed_ to be there? Did something go awry in the auto build of this Makefile? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Host down message on localhost client
On Thursday 23 February 2006 18:11, Wayne Thorpe wrote: Hello, I am attempting to get the functionality of AMANDA down and during the initial testing locally. I am discarding tape data by putting 'tapedev null: ' in amanda.conf. When I run amcheck, I receive the a host down message even though my backup backup client is on the same host as server, my system is a solaris 10: [host] ~ amcheck ProtoLocal Amanda Tape Server Host Check - WARNING: tapedev is null:, dumps will be thrown away Holding disk /amanda-vtapes-local/ProtoLocal: 9375682 KB disk space available, that's plenty NOTE: skipping tape checks NOTE: info dir /usr/adm/amanda/ProtoLocal/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.002 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.027 seconds, 1 problem found (brought to you by Amanda 2.4.4) Why are you using localhost? It is not, and never will be, a unique address, and amanda gets a tummy ache because of it. Please use the FQDN of the machine, as it exists in the /etc/hosts file, or an alias that is also listed in that file. __ My log file reads: [host] /usr/adm/amanda/ProtoLocal more log.20060223.0 START driver date 20060223 DISK planner localhost /itrn1 START planner date 20060223 INFO planner Adding new disk localhost:/itrn1. START taper datestamp 20060223 label [fake-label] tape 0 WARNING taper tapedev is null:, dumps will be thrown away ERROR planner Request to localhost timed out. FINISH planner date 20060223 WARNING driver WARNING: got empty schedule from planner STATS driver startup time 30.035 INFO taper tape [fake-label] kb 0 fm 0 [OK] FINISH driver date 20060223 time 30.055 A portion of my dump.1 reads: [host] /usr/adm/amanda/ProtoLocal more amdump.1 . . . GETTING ESTIMATES... driver: started dumper0 pid 1632 driver: started dumper1 pid 1633 driver: started dumper2 pid 1634 driver: started dumper3 pid 1635 taper: pid 1631 executable taper version 2.4.4 dumper: dgram_bind: socket bound to 0.0.0.0.753 dumper: pid 1632 executable dumper0 version 2.4.4, using port 753 taper: page size is 8192 taper: buffer size is 32768 dumper: dgram_bind: socket bound to 0.0.0.0.754 dumper: pid 1633 executable dumper1 version 2.4.4, using port 754 dumper: dgram_bind: socket bound to 0.0.0.0.755 ___ /etc/services reads: #amanda amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp /etc/inetd.conf #amanda amanda dgram udp wait amanda /opt/sfw/libexec/amandad amandad amandaidx stream tcp nowait amanda /opt/sfw/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /opt/sfw/libexec/amidxtaped amidxtaped -- - Yahoo! Mail Use Photomail to share photos without annoying attachments. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Problems building 2.5 B2
On Thu, Feb 23, 2006 at 07:24:34PM -0500, stan wrote: I'm trying to compile 2.5 beta 2 on Solaris 10 X86. The build is failing in the man subdirectory. It's complaining about this line in the generated Makefile: The actual complaint is often a big help to those answering. $(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl $(XSLTPROC) --path xslt/ --output $@ man.xsl $ Now, it's been a while since I wrote Makefiles, but I must admit that I don't undrstand rh %: myself. I don't either. Doesn't look right to me. You could try that old standby, vi, and edit it out of there. If it makes the manpages and completes, it probably was extraneous. Anyone know what's _suuposed_ to be there? Did something go awry in the auto build of this Makefile? A few years ago a makefile creation bug creapt into amanda whereby a newline was omitted. Maybe something trivial like that. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problems building 2.5 B2
On Thursday 23 February 2006 22:38, Jon LaBadie wrote: The actual complaint is often a big help to those answering. $(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl $(XSLTPROC) --path xslt/ --output $@ man.xsl $ Now, it's been a while since I wrote Makefiles, but I must admit that I don't undrstand rh %: myself. I have to confess that this is my doing. That line is a static pattern, which is different from an implicit rule in that it applies only to the given targets (in this case, man_MANS). However, it would seem that your make does not support static patterns. Try the attached patch, and let me know what happens. Implicit rules hurt make's performance (especially global ones like this), but there are not many targets in that directory anyway, so it is probably not a problem. --Ian -- Wiki for Amanda documentation: http://wiki.zmanda.com/ Index: man/Makefile.am === RCS file: /cvsroot/amanda/amanda/man/Makefile.am,v retrieving revision 1.31 diff -r1.31 Makefile.am 94c94 $(man_MANS): %: xml-source/%.proc.xml $(srcdir)/xslt/man.xsl --- %: xml-source/%.proc.xml $(srcdir)/xslt/man.xsl
