I am using the same version as you do but my amandaidx file is different than yours. Maybe it is the reason
service amandaidx
{
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/local/libexec/amindexd
disable = no
}
This is my file named amindex [EMAIL PROTECTED] wrote:
Hi,
i have successfully made a backup with amanda 2.4.4p2 (self-compiled). Great! But now i run into problems recovering the data. Any hints would be greatly appreciated... This is my file named amindex
kirk:/var/log/amanda # amrecover -C full AMRECOVER Version 2.4.4p2. Contacting server on kirk ... amrecover: Unexpected end of file, check amindexd*debug on server kirk
The amindex debug file: kirk:/var/log/amanda # cat amindexd.20040506172642.debug amindexd: debug 1 pid 17865 ruid 37 euid 37: start at Thu May 6 17:26:42 2004 amindexd: version 2.4.4p2
and the amrecover debug file: kirk:/var/log/amanda # cat amrecover.20040506172642.debug amrecover: debug 1 pid 17864 ruid 0 euid 0: start at Thu May 6 17:26:42 2004 amrecover: stream_client_privileged: connected to 192.168.1.74.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.762 service amandaidx { socket_type = stream protocol = tcp wait = no user = amanda group = disk server = /usr/local/libexec/amindexd disable = no }
That's all. To me it seems like the amindex daemon is
making trouble, although the .amandahosts file is ok.
This is my xinetd entry for amindex: kirk:/var/log/amanda # cat /etc/xinetd.d/amandaidx service amandaidxservice amandaidx { socket_type = stream protocol = tcp wait = no user = amanda group = disk server = /usr/local/libexec/amindexd disable = no }
{ socket_type = stream protocol = tcp wait = no user = amanda server = /usr/lib/amanda/amindexd groups = yes server_args = amindexd }
And here the amandahosts file:
[EMAIL PROTECTED]:/home/kai> cat ~/.amandahosts kirk.bbaw.de amanda kirk.bbaw.de root kirk.bbaw.de
Any ideas?
thanks,
Kai
