On Tue, 28 Jan 2003, Riccardo Parola wrote:

> [root@tigger testrest]# amrecover -s garfield -C Daily-Backup-Set1
> AMRECOVER Version 2.4.2p2. Contacting server on garfield ...
> 220 garfield AMANDA index server (2.4.2p2) ready.
> 200 Access OK
> Setting restore date to today (2003-01-28)
> 200 Working date set to 2003-01-28.
> 200 Working date set to 2003-01-28.
> amrecover: Unexpected server end of file
>
> I've seen this is a common thing, usually solved very easily but I must be
> missing something.

Riccardo,

I get the same message when the config specified is either misspelled or
wrong.  Example:

bash-2.05# /usr/local/sbin/amrecover -s my.tape.server.com -t my.tape.server.com
AMRECOVER
Version 2.4.2p2. Contacting server on amanda1.my.domain.com ...
220 amanda1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-01-29)
200 Working date set to 2003-01-29.
200 Working date set to 2003-01-29.
amrecover: Unexpected server end of file


When I specify it:

bash-2.05# /usr/local/sbin/amrecover -s my.tape.server.com -t 
my.tape.server.com -C standard
AMRECOVER Version 2.4.2p2. Contacting server on amanda1.my.domain.com ...
220 amanda1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-01-29)
200 Working date set to 2003-01-29.
200 Config set to standard.


The problem could be due to other causes.  You should check
/tmp/amanda/amindex*.debug on your amanda server.

Regards,

-gordon