Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*problem\s+with\s+amdump\s*$/: 8 ]

Total 8 documents matching your query.

1. problem with amdump (score: 1)
Author: nejat onay erkose <nejat_onay.erkose AT int-evry DOT fr>
Date: Thu, 06 May 2004 16:08:08 +0200
Hello , DISK planner amandatux.int-evry.fr /home/noe START planner date 20040506 INFO planner Adding new disk amandatux.int-evry.fr:/home/noe. START driver date 20040506 FAIL planner amandatux.int-ev
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2004-05/msg00061.html (12,008 bytes)

2. Re: problem with amdump (score: 1)
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Thu, 6 May 2004 10:22:01 -0400 (EDT)
And what does sendsize*debug and/or amandad*debug on the client have to say? Err, if you haven't backed anything up yet, what files would there be to recover? -- Joshua Baker-LePain Department of Bio
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2004-05/msg00062.html (11,279 bytes)

3. Re: problem with amdump (score: 1)
Author: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 06 May 2004 16:24:03 +0200
Probably, but we can't tell you... At least not from the information you gave. What did amcheck say? Did you at least try to solve this yourself by trying to understand what amanda needs to do? Confi
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2004-05/msg00063.html (12,491 bytes)

4. Re: problem with amdump (score: 1)
Author: nejat onay erkose <nejat_onay.erkose AT int-evry DOT fr>
Date: Thu, 06 May 2004 16:51:36 +0200
Here is the sendsize debug file... sendsize: debug 1 pid 14004 ruid 33 euid 33: start at Thu May 6 15:54:31 2004 sendsize: version 2.4.4p2 sendsize[14006]: time 0.003: calculating for amname '/home/n
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2004-05/msg00065.html (13,113 bytes)

5. problem with amdump (score: 1)
Author: manjit AT notay DOT net
Date: Fri, 23 May 2003 10:51:21 +0100
This has probably been answered before but please bare with me as im new and at then end of my rope. This my last resort hope you can help. I installed amanda 2.4.4 successfully and after configuring
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-05/msg00524.html (11,158 bytes)

6. Re: problem with amdump (score: 1)
Author: Mats Blomstrand <mats.blomstrand AT htu DOT se>
Date: Fri, 23 May 2003 12:05:40 +0200
What is the owner/group/access-bits on the devices? I have this on mine (a linux system): $ ls -ld /dev/nst0 /dev/sg0 crw-rw-- 1 amanda disk 9, 128 Aug 30 2001 /dev/nst0 crw-rw-- 1 root amanda 21, 0
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-05/msg00526.html (10,791 bytes)

7. Re: problem with amdump (score: 1)
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Fri, 23 May 2003 06:12:48 -0400
Chuckle... And using localhost bites man again says the headline. :) The docs recommend against that, but it seems everyone has to learn it anew. Your disklist should use FQDN's exclusively. And don'
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-05/msg00527.html (12,104 bytes)

8. Re: problem with amdump (score: 1)
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Fri, 23 May 2003 09:15:26 -0400 (EDT)
Don't use localhost, as has been said by others. Are you using inetd or xinetd? What does your amanda entry look like? What's in /tmp/amanda/amdandad*debug. -- Joshua Baker-LePain Department of Biome
/usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-05/msg00533.html (11,140 bytes)


This search system is powered by Namazu