I (believe) i ran into the same bug:
minnie:~# amrecover -C $myconfig
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
[request failed: timeout waiting for ACK]
minnie:~# amrecover -C $myconfig -s localhost
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
[request failed: timeout waiting for ACK]
but this works (!)
minnie:~# amrecover -C fizzback -s 127.0.0.1
AMRECOVER Version 2.5.2p1. Contacting server on 127.0.0.1 ...
NAK: user root from localhost is not allowed to execute the service amindexd:
Please add "amindexd amidxtaped" to the line in /home/backup/.amandahosts on
the client
(ignore the permission bit - the important thing is that it actually
ends up *talking* to amandad...)
Looking at the strace(1) output of amrecover, i see this:
sendto(3, "Amanda 2.5 REQ HANDLE 000-0000000"..., 136, 0, {sa_family=AF_INET6,
sin6_port=htons(10080), inet_pton(AF_INET6, "::1", &sin6_addr),
sin6_flowinfo=0, sin6_scope_id=0}, 28) = 136
towards the end... So perhaps the problem is that amrecover is trying to
use IPv6, rather than IPV4?
My versions:
* amanda-client: 1:2.5.2p1-4
* amanda-common: 1:2.5.2p1-4
* libc6: 2.7-16
* openbsd-inetd: 0.20080125-2
Hope this helps
--
Karl E. Jørgensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
