Re: Problem with recover from new amanda Server
2006-07-20 12:40:28
I think you are missing the "amidxtaped" part of the amanda server xinetd
config.
Here is an example of what you server xinetd config should look like. After you
make
the changes make sure to restart xinetd and also tail /var/log/messages for any
possible
errors. The run "amrecover TEST -t amanda-test -s amanda-test" from the client
as root.
# default: on
#
# description: These services provide indexing capabilities for
# the Amanda backup server.
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/lib/amanda/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/lib/amanda/amidxtaped
}
Sebastian Kösters wrote:
Hi!
A few days ago i setup a new amanda server on an new machine.
Everything seems to be fine. I did a test-backup and it works great (pretty
fast).
I also wanted to try to recover this test-backup. But when i do
amrecover -t amanda-test -s amanda-test -C TEST
i get this error:
amrecover: Unexpected end of file, check amindexd*debug on server
amanda-test
Thats in amindexd*debug:
mindexd: debug 1 pid 6081 ruid 33 euid 33: start at Thu Jul 20 10:36:30 2006
amindexd: version 2.4.5p1
amindexd: getpeername: Socket operation on non-socket
amindexd: time 0.000: getpeername: Socket operation on non-socket
amindexd: time 0.000: pid 6081 finish time Thu Jul 20 10:36:30 2006
my xinetd entry looks like this:
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/lib/amanda/amindexd
disable = no
}
When i execute /usr/lib/amanda/amindexd by hand i get no error message or
something like this.
What am i doing wrong?
Hope someone can help.
Thanks!
Kind regards
Sebastian
|
|
|