Hi,
first i will use amoldrecover for recover ;-)
why didn´t i remember this before...
Thats not solving the problem, but it is a work arround.
This afternoon i will leave to vacation.
Will work on this at a later time.
Thanks for help.
bye
B²
Bjoern B schrieb:
Hi,
Jean-Louis Martineau s
Hi,
Jean-Louis Martineau schrieb:
Can you upgrade to 2.5.2p1?
would not to be my preferred way. I like my aptitude get update thing.
But i will look if there is a real reason for not upgrading.
When i upgrade i will use the configure options for the 2.5.1.p1 Debian
package or what should i t
Can you upgrade to 2.5.2p1?
Jean-Louis
Bjoern B wrote:
Hi,
Jean-Louis Martineau schrieb:
The only way to get this error is if amandad doesn't get "amindexd"
as argument.
But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have char
Hi,
Jean-Louis Martineau schrieb:
Frank Smith wrote:
amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:
<
ERROR amindexd: invalid service
My interpretation of this error is that it couldn't find the service
named amindexd. Is this something new in 2
Hi,
Jean-Louis Martineau schrieb:
The only way to get this error is if amandad doesn't get "amindexd" as
argument.
But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character you
don't see.
I have retyped the server_args in
Frank Smith wrote:
amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:
<
ERROR amindexd: invalid service
My interpretation of this error is that it couldn't find the service
named amindexd. Is this something new in 2.5, as in 2.4 it was named
amandaidx
The only way to get this error is if amandad doesn't get "amindexd" as
argument.
But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character you
don't see.
Verify that you doesn't have an amandad process already running.
Jean-
Bjoern B wrote:
> Hi,
>
> you are right i mean amrecover. sorry
>
> Jean-Louis Martineau schrieb:
>> Your config looks good, are you sure you restarted xinetd?
>
> I did a /etc/init.d/xinetd restart
>
> To be sure, i have done a server restart and tested it again.
> Same message.
>
>> amrecove
Hi,
you are right i mean amrecover. sorry
Jean-Louis Martineau schrieb:
Your config looks good, are you sure you restarted xinetd?
I did a /etc/init.d/xinetd restart
To be sure, i have done a server restart and tested it again.
Same message.
amrecover in 2.4.* will use the amandaidx and a
amrestore doesn't use the network and can't fail with "NAK: amindexd:
invalid service".
amrestore and amrecover are two distinct commands, don't say amrestore
when you talk about amrecover, it's really confusing.
Your config looks good, are you sure you restarted xinetd?
amrecover in 2.4.* wil
Hi,
here i go again.
Backup works now, but i can´t recover.
Seems to be a problem, because of the bsd/bsdudp/bsdtcp authentication.
We have 3 Amandaserver running.
And a couple of clients.
Amandaserver1 = Version 2.4.2p2
Amandaserver2 = Version 2.4.4p3
Amandaserver3 = Version 2.5.1p1
There
11 matches
Mail list logo
