On Friday 28 April 2006 05:31, Thomas Ginestet wrote:
>Gene Heskett a écrit :
>
>Thanks a lot Gene (and you too Matt ;-) ), your script is such a good
> idea. Using the x bit was better ;-). But I have others problems like
> the generated tapelist with owner amanda and group amanda (and
> restricte
Gene Heskett a écrit :
On Thursday 27 April 2006 07:56, Thomas Ginestet wrote:
[...]
501 Could not read config file /etc/amanda/DailySet/amanda.conf!
I've checked amindexd logs:
backup:/var/log/amanda# vi amindexd.20060426132954.debug
amindexd: debug 1 pid 12531 ruid 34 euid 34: start at
On Thursday 27 April 2006 07:56, Thomas Ginestet wrote:
[...]
>>>501 Could not read config file /etc/amanda/DailySet/amanda.conf!
>>>
>>>
>>>I've checked amindexd logs:
>>>
>>>backup:/var/log/amanda# vi amindexd.20060426132954.debug
>>>
>>>amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed A
On Thu, Apr 27, 2006 at 01:56:51PM +0200, Thomas Ginestet enlightened us:
> Gene Heskett a écrit :
>
> >On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
> >
> >
> >>Hi list,
> >>
> >>Thanks to your help, I've successful launched amcheck and amdump :-)
> >>I've tried amrecover to check rec
Gene Heskett a écrit :
On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
Hi list,
Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems
occured.
After playing with access not allowed error, I'm still st
On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
>Hi list,
>
>Thanks to your help, I've successful launched amcheck and amdump :-)
>I've tried amrecover to check recovery too but some new problems
> occured.
>
>After playing with access not allowed error, I'm still stuck on the
>following
Hi list,
Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems occured.
After playing with access not allowed error, I'm still stuck on the
following one:
backup:/# amrecover DailySet
AMRECOVER Version 2.5.0. Co
>
> Actually, I did mean "runtar", a program in the amanda
> distribution. It lives in the libexec directory. It should be
> suid-root and owned by root, and, if located on an nfs-share,
> the share should be mounted with options to enable suid-root bits:
>
> -rwsr-x---1 root bin
Gerhardus Geldenhuis wrote:
The xinetd is configured correctly so that is not a problem.
You say so, but we can't check it.
Post the xinetd config for amanda and the result of "id" executed as
user amanda.
Thanks. Checked and indeed correct.
When using gnutar, a frequent error is the lost suid-b
> >
> > The xinetd is configured correctly so that is not a problem.
>
> You say so, but we can't check it.
> Post the xinetd config for amanda and the result of "id" executed as
> user amanda.
>
> When using dump, a frequent error is that primary group has
> no access to the diskdevice. Addi
Gerhardus Geldenhuis wrote:
Hi
I am trying to backup 5 clients currently of which 2 does not want to
work for some reason.
The error I get is:
ERROR: rian-dlin: [could not access /home/oscar3/SciFi
(/home/oscar3/SciFi): Permission denied]
ERROR: rukh: [could not access /u/oscar3/dev (/u/oscar3/dev)
Hi
I am trying to backup 5 clients currently of which 2 does not want to
work for some reason.
The error I get is:
ERROR: rian-dlin: [could not access /home/oscar3/SciFi
(/home/oscar3/SciFi): Permission denied]
ERROR: rukh: [could not access /u/oscar3/dev (/u/oscar3/dev): Permission
denied]
I can
On Tuesday 05 August 2003 02:04, rehanann wrote:
>In Red hat 8 amanda 2.4.2p1 is already installed with Amanda user I
> have only problem with permission on the tape device.
>Amanda cannot dump with root login when I SU to Amanda and try
> amdump it gives me permission denied error after checking a
In Red hat 8 amanda
2.4.2p1 is already installed with Amanda user I have only problem with
permission on the tape device.
Amanda cannot dump with root login when I SU to Amanda and try
amdump it gives me permission denied error after
checking amcheck.
Also with sudo it will not work
beca
I don't know if this was the cause or not but:
The machine thames has two IP addresses. One on eth0, the other on eth0:1.
Once I added both addresses to the host file on _both_ machines, amrecover
happily restored the file. I'll admit I have no idea why this should make a
difference, tho.
I am having a permission problem with amrecover that makes no sense to me.
Please cc me on any replies. I am a memebr of the list but I haven't seen any
mail in a while
$ sudo amrecover -C daily1 -s chena
AMRECOVER Version 2.4.3b2. Contacting server on chena ...
220 chena AMANDA index s
On Friday 20 September 2002 15:43, Caitlyn M. Martin wrote:
>On Fri, 2002-09-20 at 15:07, Gene Heskett wrote:
>> I should have qualified that by saying the tarballs installer
>> won't. I have NDI whether the rpm does or not.
>
>I did use the rpms, I did reinstall, and everything worked. I
> have
On Fri, 2002-09-20 at 15:07, Gene Heskett wrote:
> I should have qualified that by saying the tarballs installer won't.
> I have NDI whether the rpm does or not.
I did use the rpms, I did reinstall, and everything worked. I have no
clue what went wrong the first time. All I know I successful
On Friday 20 September 2002 11:06, Gene Heskett wrote:
>On Friday 20 September 2002 10:03, Caitlyn M. Martin wrote:
>>Hi, Gene,
>
>[...]
>
>>As I said in my response to Frank, I'm going to rip everything
>> out (after saving my amanda.conf file and disklist file) and
>> start over.
>
>The saveing
On Friday 20 September 2002 10:03, Caitlyn M. Martin wrote:
>Hi, Gene,
[...]
>As I said in my response to Frank, I'm going to rip everything out
>(after saving my amanda.conf file and disklist file) and start
> over.
The saveing isn't required, if they exist, they are not overwritten
by the inst
Caitlyn M. Martin wrote:
>Hi, Gene,
>
>
>>The only thing that comes to mind quickly is probably related to the
>>question/statement "you do have a user amanda, who is a member of
>>group disk, don't you?"
>>
>>
>
>Yes, of course. I think that was done automagically when I installed
>the
Hi, Gene,
>
> The only thing that comes to mind quickly is probably related to the
> question/statement "you do have a user amanda, who is a member of
> group disk, don't you?"
Yes, of course. I think that was done automagically when I installed
the amanda rpms.
As I said in my response to F
Hi, Frank, and everyone else.
>
> My guess is that the permission problem is higher up. Try
> su - amanda
> and then try to cd down the directory structure. The index,
> pip, and _users5 directories should be created automatically
> during the backup run. As the amanda us
On Thursday 19 September 2002 17:15, Caitlyn M. Martin wrote:
>Hi, everyone,
>
>OK, I admit it. amanda is kicking my you-know-what.
>
>amdump is failing because it's unable to write it's index files.
> Why? From the errors it looks like a permissions problem, but the
> directory is owned by aman
ip/_users5/20020919_0.gz.tmp: Permission
> denied]
>
> This is amanda 2.4.2p2 running on Red Hat 7.3.94 (null/RH8 beta).
>
> OK, I'm still doing something simple and stupid wrong. Any clues what
> that might be?
>
> Thanks,
> Caity
My guess is that the permission p
Hi, everyone,
OK, I admit it. amanda is kicking my you-know-what.
amdump is failing because it's unable to write it's index files. Why?
>From the errors it looks like a permissions problem, but the directory
is owned by amanda and right now I've got everything opened up to chmod
777. There e
HI,
I am running Amanda 2.4.2p2 with ftape-3212002 and everything was
working fine until I installed a scsci-2 HP Surestore T4 tape drive.
When I run amcheck on the conf file I get the following error:
Amanda Tape Server Host Check
-
Holding disk /amanda: 1342540
On Mon, 1 Jul 2002 at 3:31pm, Soo Hom wrote
> I am getting this error on a new client I added:
> Amanda Backup Client Hosts Check
>
> ERROR: song3: [can not access /dev/rdsk/c0t0d0s7 (c0t0d0s7): Permission
> denied]
You need to make sure that the amanda user has
On Mon, Jul 01, 2002 at 03:31:29PM -0700, Soo Hom wrote:
> Hello,
>
> I am getting this error on a new client I added:
> Amanda Backup Client Hosts Check
>
> ERROR: song3: [can not access /dev/rdsk/c0t0d0s7 (c0t0d0s7): Permission
> denied]
> ERROR: song3: [can not
Hello,
I am getting this error on a new client I added:
Amanda Backup Client Hosts Check
ERROR: song3: [can not access /dev/rdsk/c0t0d0s7 (c0t0d0s7): Permission
denied]
ERROR: song3: [can not access /dev/rdsk/c0t0d0s4 (c0t0d0s4): Permission
denied]
ERROR: song3: [
Hi,
Typo in inetd.conf for the amidxtaped service.
Thanks much,
Pam
On Mon, 18 Jun 2001, John R. Jackson wrote:
> >amrecover: error reading tape: Connection reset by peer
>
> Do you have amidxtaped set up in inetd.conf (or xinetd) on "stheno"?
> Is it set up the same way amindexd is (e.g. T
>amrecover: error reading tape: Connection reset by peer
Do you have amidxtaped set up in inetd.conf (or xinetd) on "stheno"?
Is it set up the same way amindexd is (e.g. TCP wrappers)? Is there
a /tmp/amanda/amidxtaped*debug? If so, what's in it?
John R. Jackson, Technical Software Specialist,
I've been struggling trying to get Amanda running on a FreeBSD 4.3-STABLE
box with a HP SureStore 12000E 6-tape DAT changer for what seems like an
eternity now.
I first tried installing via the FreeBSD ports collection. That was version
2-4-2p2. I could not get any of the changer scripts that b
Hi,
/home/pam is NFS mounted elsewhere and root was not allowed
access. Giving root access fixed the problem. Thanks.
Now, I'm trying to amrecover what was backed up on Medusa from Medusa and
am getting
amrecover: error reading tape: Connection reset by peer
extract_list - child returned non-zer
>? gtar: Cannot open
>/home/pam/amanda-2.4.2p2/var/amanda/gnutar-lists/medusa_var_tmp_pam_0.new:
>Permission denied
At this point, Amanda is running gtar as root. Can root access this
area from the clients that are failing? For instance, is /home/pam NFS
mounted from someplace? Is root allowed
35 matches
Mail list logo
