Re: help getting started
Hi, I'm getting some errors in my amstatus output - can anyone enlighten me? # su amanda -c /usr/sbin/amstatus DailySet1 Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004 localhost:/etc 2 24k finished (16:46:53) Use of uninitialized value in printf at /usr/sbin/amstatus line 760. Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 761. localhost:/home 017720729k dumping0k (16:49:27) Use of uninitialized value in addition (+) at /usr/sbin/amstatus line 770. localhost:/usr/local 0 22701k finished (16:47:32) localhost:/var 0 232660k wait for dumping driver: (aborted) SUMMARY part real estimated size size partition : 4 estimated : 4 17976128k flush : 00k failed : 0 0k ( 0.00%) wait for dumping: 1 232660k ( 1.29%) dumping to tape : 0 0k ( 0.00%) dumping : 10k 17720729k ( 0.00%) ( 0.00%) dumped : 222725k22739k ( 99.94%) ( 0.13%) wait for writing: 00k0k ( 0.00%) ( 0.00%) wait to flush : 00k0k (100.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 222725k22739k ( 99.94%) ( 0.13%) 3 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 67 holding space : 296960k (100.00%) dumper0 busy : 0:02:17 ( 88.75%) taper busy : 0:00:10 ( 6.90%) 0 dumpers busy : 0:00:17 ( 10.98%) start-wait: 0:00:17 (100.00%) 1 dumper busy : 0:02:17 ( 89.02%)no-bandwidth: 0:01:49 ( 79.46%) start-wait: 0:00:28 ( 20.54%) It seems to be taking ages to complete this backup...is something wrong? Max. Max Waterman wrote: Thanks everyone for helping. I got email working (albeit only locally since my isp is blocking my [chinese] IP address), so now I can get the reports. I bought some more tapes, and have used the amrmtape command to start from scratch. Seems to be working like a charm. Next step is 'day 4' :) http://www.harkness.co.uk/services/backup.html Thanks again...until next time. Max. Paul Bijnens wrote: Max Waterman wrote: I am not really sure. Maybe this : driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite active tape DailySet101] It seems that the very first time you ran the backup for '/etc' it worked fine. See: http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail ) This is how a normal run looks like. For the next test, you seem to be using the same tape. But you instructed to amanda (tapecycle XXX) that she will not overwrite an active tape. So she cannot write to that tape. She falls back to so called degraded mode backups dumping to the holdingdisk. You also have specified reserve 100 (that's the default if you didn't change it), meaning that in degraded mode, 100% of the holdingdisk is reserved for incremental backups. But the only disklistentry was a new one, and amanda cannot make an incremental backup when there is no full backup to base it on. Then she gives up. Solution: while testing, you can amrmtape the testing tape, or you need to give more tapes (until you have tapecycle number of tapes).
Re: help getting started
Hi, Max, on Mittwoch, 30. Juni 2004 at 13:06 you wrote to amanda-users: MW Hi, MW I'm getting some errors in my amstatus output - can anyone enlighten me? # su amanda -c /usr/sbin/amstatus DailySet1 Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004 localhost:/etc 2 24k finished (16:46:53) Use of uninitialized value in printf at /usr/sbin/amstatus line 760. Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 761. localhost:/home 017720729k dumping 0k (16:49:27) Use of uninitialized value in addition (+) at /usr/sbin/amstatus line 770. localhost:/usr/local 0 22701k finished (16:47:32) localhost:/var 0 232660k wait for dumping driver: (aborted) MW It seems to be taking ages to complete this backup...is something wrong? yes, it is. Those uninitialized values should not be there. A quick look into amstatus seems to lead us to the estimates But the estimates seem to succeed. What release of AMANDA is this, btw? At first edit your disklist. Don't use localhost, use the full hostname instead. Read docs/TOP-TEN-QUESTIONS for the explanation, if you want. Stefan
[no subject]
auth 9a7ee70a subscribe amanda-users [EMAIL PROTECTED] -- Daniel García Franco e-mail: [EMAIL PROTECTED] SADIEL, S.A. C\ Isaac Newton s/n, Edificio Sadiel, Isla de la Cartuja C.P. 41002 SEVILLA Tlf: +34 955043600 (83736) Fax: 955043601 http://www.sadiel.es e-mail: [EMAIL PROTECTED]
Re: help getting started
Max Waterman wrote: I'm getting some errors in my amstatus output - can anyone enlighten me? # su amanda -c /usr/sbin/amstatus DailySet1 Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004 localhost:/etc 2 24k finished (16:46:53) Use of uninitialized value in printf at /usr/sbin/amstatus line 760. This seems to be produced by amanda 2.4.3. Not sure of the cause, but just that part in the amstatus code (among others) got updated in 2.4.4. The most recent stable version is 2.4.4p3. I guess upgrading will at least gid rid of that error message. ... localhost:/home 0 17720729k dumping 0k (16:49:27) (reformatted the above line, and added a space) So this seems to be a 17 Gbyte partition. And it seems to be dumping directly to tape, bypassing the holdingdisk. Am I correct? It seems to be taking ages to complete this backup...is something wrong? I don't know. How long is it running? How long would it take to write 17 Gbyte to tape at full speed? Maybe your tapedrive is not streaming anymore, because the bypassing of the holdingdisk? If the datastream cannot follow the speed of the tapedrive, the drive has to stop/backup a little/restart and this has tremendous influence on the throughput (not to mention the wear and tear on the drive and the cartridge!!!). If this is indeed the case, possible solutions are: - use a larger holdingdisk - divide /home in smaller chunks, each fitting into the holdingdisk (best is fitting at least two of them: one taping and rest dumping) See docs/disklist in the sources for an example how to do this. - disable software compression if cpu is the bottleneck (amstatus in amanda 2.4.4p3 also has better indications of dumps that bypass holdingdisk. Another reason to upgrade.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: help getting started
Hi, Max, on Mittwoch, 30. Juni 2004 at 14:01 you wrote to amanda-users: MW | Read docs/TOP-TEN-QUESTIONS for the explanation, if you want. MW Unfortunately, www.amanda.org is still not accessible from China :( MW I guess I can try one of the anonymous proxys, but they also, MW unsuprisingly, tend not to work very well from here either. MW Is there a mirror somewhere, is the relevant info installed with amanda? MW I see there's a fair bit of info. I'll dig some...esp. FAQ that's there. This is ALPHA-stage when it comes to formatting, but the content is the same as in the AMANDA-tarball: http://www.oops.co.at/AMANDA-docs/index.html There you can also find the top-ten ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: help getting started
On Wednesday 30 June 2004 07:06, Max Waterman wrote: Hi, I'm getting some errors in my amstatus output - can anyone enlighten me? # su amanda -c /usr/sbin/amstatus DailySet1 Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 CST 2004 localhost:/etc 2 24k finished Please re-read the fAQ and the TOP-TEN-QUESTIONS in the docs dir, and then give your machine a unique name. localhost is not unique. (16:46:53) Use of uninitialized value in printf at /usr/sbin/amstatus line 760. Use of uninitialized value in numeric ne (!=) at /usr/sbin/amstatus line 761. localhost:/home 017720729k dumping0k (16:49:27) Use of uninitialized value in addition (+) at /usr/sbin/amstatus line 770. localhost:/usr/local 0 22701k finished (16:47:32) localhost:/var 0 232660k wait for dumping driver: (aborted) SUMMARY part real estimated size size partition : 4 estimated : 4 17976128k flush : 00k failed : 0 0k ( 0.00%) wait for dumping: 1 232660k ( 1.29%) dumping to tape : 0 0k ( 0.00%) dumping : 10k 17720729k ( 0.00%) ( 0.00%) dumped : 222725k22739k ( 99.94%) ( 0.13%) wait for writing: 00k0k ( 0.00%) ( 0.00%) wait to flush : 00k0k (100.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 222725k22739k ( 99.94%) ( 0.13%) 3 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 67 holding space : 296960k (100.00%) dumper0 busy : 0:02:17 ( 88.75%) taper busy : 0:00:10 ( 6.90%) 0 dumpers busy : 0:00:17 ( 10.98%) start-wait: 0:00:17 (100.00%) 1 dumper busy : 0:02:17 ( 89.02%) no-bandwidth: 0:01:49 ( 79.46%) start-wait: 0:00:28 ( 20.54%) It seems to be taking ages to complete this backup...is something wrong? When it is done, what speed is reported in the email the dump sends you? By that, I mean does it match within say 10% of the drives rated speed of data transfer? Also, note the holding disk area of only 296,960k, (297 megs) which is not nearly enough for amdump to stuff a 17,720,729k (18Gb? break that into subdirs and use tar, not dump if thats what you are now using) dump, and this is forceing amdump to write directly to the tape, possibly with lots of under-runs that will result in the drive stopping, backing up and restarting (shoe shining) which takes time out of the write time, so I'd expect the write speeds reported to be a bit slow. So in addition to giving the machine a unique name that can at least be resolved in the /etc/hosts file, find it some more holding disk area. The localhost issue probably won't effect the backups, but it sure will mung any chances of a clean recovery should you need it. Max. Max Waterman wrote: Thanks everyone for helping. I got email working (albeit only locally since my isp is blocking my [chinese] IP address), so now I can get the reports. I bought some more tapes, and have used the amrmtape command to start from scratch. Seems to be working like a charm. Next step is 'day 4' :) http://www.harkness.co.uk/services/backup.html Thanks again...until next time. Max. Paul Bijnens wrote: Max Waterman wrote: I am not really sure. Maybe this : driver: result time 6.776 from taper: TAPE-ERROR [cannot overwrite active tape DailySet101] It seems that the very first time you ran the backup for '/etc' it worked fine. See: http://reality.sgiweb.org/maxw/tmp/amanda/log.20040623.0.mail ) This is how a normal run looks like. For the next test, you seem to be using the same tape. But you instructed to amanda (tapecycle XXX) that she will not overwrite an active tape. So she cannot write to that tape. She falls back to so called degraded mode backups dumping to the holdingdisk. You also have specified reserve 100 (that's the default if you didn't change it), meaning that in degraded mode, 100% of the holdingdisk is reserved for incremental backups. But the only disklistentry was a new one, and amanda cannot make an incremental backup when there is no full backup to base it on. Then she gives up. Solution: while testing, you can amrmtape the testing tape, or you need to give more tapes (until you have tapecycle number of tapes). -- Cheers, Gene There are 4 boxes to be used in defense of liberty. Soap, ballot, jury, and ammo. Please use in that order, starting now. -Ed Howdershelt, Author Additions to this message made by Gene Heskett are Copyright 2004, Maurice E. Heskett, all rights reserved.
Re: help getting started
On Wednesday 30 June 2004 08:01, Max Waterman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan G. Weichinger wrote: | Hi, Max, | | on Mittwoch, 30. Juni 2004 at 13:06 you wrote to amanda-users: | | MW Hi, | | MW I'm getting some errors in my amstatus output - can anyone enlighten me? |# su amanda -c /usr/sbin/amstatus DailySet1 |Using /var/lib/amanda/DailySet1/amdump from Wed Jun 30 16:46:16 | CST 2004 | |localhost:/etc 2 24k finished | (16:46:53) Use of uninitialized value in printf at | /usr/sbin/amstatus line 760. Use of uninitialized value in | numeric ne (!=) at /usr/sbin/amstatus line 761. |localhost:/home 017720729k dumping | 0k (16:49:27) |Use of uninitialized value in addition (+) at /usr/sbin/amstatus | line 770. |localhost:/usr/local 0 22701k finished | (16:47:32) localhost:/var 0 232660k | wait for dumping driver: (aborted) | MW It seems to be taking ages to complete this backup...is | something wrong? | yes, it is. Those uninitialized values should not be there. A | quick look into amstatus seems to lead us to the estimates | | But the estimates seem to succeed. | | What release of AMANDA is this, btw? 2.4.3-4, it seems. Humm, would it be possible for one of us to email you a more recent tar.gz of say 2.4.5b1? The last one I have on site is dated 20040622. I'd go on an education campaign to get access to www.amanda.org enabled, along with access to the site Jean-Louis has for new snapshots at http://www.iro.umontreal.ca/~marinea/amanda. Only by severe miss-information on the part of the chinese filtering folks would they set a block on those two sites. | At first edit your disklist. | | Don't use localhost, use the full hostname instead. OK, that's easy :) | Read docs/TOP-TEN-QUESTIONS for the explanation, if you want. Unfortunately, www.amanda.org is still not accessible from China :( I guess I can try one of the anonymous proxys, but they also, unsuprisingly, tend not to work very well from here either. Is there a mirror somewhere, is the relevant info installed with amanda? I see there's a fair bit of info. I'll dig some...esp. FAQ that's there. Thanks. Max. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA4qur4frZ3W7OHZMRAvaCAJ91f8tCvD5nPYi7IQR9QTbi9VbbhACeOTvU B3ncR50BIUykoH30KQS/faQ= =btYK -END PGP SIGNATURE- -- Cheers, Gene There are 4 boxes to be used in defense of liberty. Soap, ballot, jury, and ammo. Please use in that order, starting now. -Ed Howdershelt, Author Additions to this message made by Gene Heskett are Copyright 2004, Maurice E. Heskett, all rights reserved.
authorisation failure
Hi, I've just upgraded my Mandrake 9.1 (under which I've had Amanda working perfectly for many moons) to Mandrake 10.0. Amanda planner is now failing: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR tony-lx: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed I can't immediately find the solution in the docs, so can someone please point me in the right direction for fixing trhis problem? TIA, Tony -- Tony van der Hoff | mailto:[EMAIL PROTECTED] Buckinghamshire England
Re: authorisation failure
On Wed, 30 Jun 2004 at 4:29pm, Tony van der Hoff wrote I've just upgraded my Mandrake 9.1 (under which I've had Amanda working perfectly for many moons) to Mandrake 10.0. Amanda planner is now failing: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR tony-lx: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed I can't immediately find the solution in the docs, so can someone please point me in the right direction for fixing trhis problem? This is probably in FAQ-O-MATIC, and certainly in the mailing list archives. You need to have an entry in .amandahosts in the amanda user's $HOME on the server that looks like this (given the above error message): tony-lx amanda -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: authorisation failure
Joshua Baker-LePain [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED] On Wed, 30 Jun 2004 at 4:29pm, Tony van der Hoff wrote I've just upgraded my Mandrake 9.1 (under which I've had Amanda working perfectly for many moons) to Mandrake 10.0. Amanda planner is now failing: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR tony-lx: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed I can't immediately find the solution in the docs, so can someone please point me in the right direction for fixing trhis problem? This is probably in FAQ-O-MATIC, and certainly in the mailing list archives. You need to have an entry in .amandahosts in the amanda user's $HOME on the server that looks like this (given the above error message): tony-lx amanda Thanks, Joshua, for both your messages. There is really no need to respond to both the list and directly. As I said, I've had Amanda working fine under Mandrake 9.1, it was the upgrade to 10.0 that caused the problem. And, yes, when I mentioned the docs, I did include FAQ-O-MATIC, and the archives. Indeed I have that entry (and one for root, to allow amrecover) in .amandahosts. However, you did give me cause to ensure that it was there :-) Does anyone have any other suggestions? -- Tony van der Hoff | mailto:[EMAIL PROTECTED] Buckinghamshire England
Re: authorisation failure
Tony van der Hoff wrote: Indeed I have that entry (and one for root, to allow amrecover) in .amandahosts. However, you did give me cause to ensure that it was there :-) Does anyone have any other suggestions? Did the use amanda's home directory change during the upgrade? So that it wouldn't look for .amandahosts in the same place anymore? Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: authorisation failure
On Wed, 30 Jun 2004 at 10:51pm, Tony van der Hoff wrote Thanks, Joshua, for both your messages. There is really no need to respond to both the list and directly. As I said, I've had Amanda working fine under SOP. How do I know you're subscribed to the list? Indeed I have that entry (and one for root, to allow amrecover) in .amandahosts. However, you did give me cause to ensure that it was there :-) And does the location of the properly filled in .amandahosts match $HOME for the amanda user specified in /etc/passwd? Are the permissions right (can the amanda user read it)? If all that checks out, look in /tmp/amanda/amandad*debug for more detail on the exact error (and post the contents here). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University