.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf!
The relevant amindexd.*.debug on the server then looks like this:
amindexd: debug 1 pid 28092 ruid 34 euid
or
directory
amindexd: time 0.003: 501 Could not read config file
/etc/amanda/amindexd/amanda.conf!
amindexd: time 0.003: 220 srv AMANDA index server (2.5.2p1) ready.
amindexd: time 0.003: ? read error: Connection reset by peer
amindexd: time 0.003: pid 28092 finish time Fri Apr 3 17:31:45 2009
Version 2.5.2p1. Contacting server on srv ...
220 srv AMANDA index server (2.5.2p1) ready.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf
. Contacting server on srv ...
220 srv AMANDA index server (2.5.2p1) ready.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf!
The relevant amindexd