I finally figured it out.  It was either a space or an empty line in 
/etc/inetd.conf.  I don't know why this matters to inetd, but it brings me 
back to my days doing vax assembly.    

This is what I had in /etc/inetd.conf:

#
[....blank line...]
# amanda backup client
 amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad
# 

When I uncommented the client entry (amanda dgram...), I must have 
accidentally left a space in the place of the # marker.  Before the top 
comment, there was a blank line.  I deleted the line as well.  After 
restarting inetd.conf, it now works!  I can now do an amrecover from the 
backup server as well as the client servers.

You were right about the tapeserver (-t) parameter.  You need to add that when 
running amrecover from a client.

Eric


> On 8/27/02 2:16 PM, "Eric Swindell" <eric.swindell AT att DOT net> wrote:
> > Tony,
> >
> > I have "index yes" in amanda.conf.  I just ran:
> > /usr/sbin/amrecover -C daily -s backup.rnd.caribbeanblue.com -t
> > backup.rnd.caribbeanblue.com -d /dev/nst0
> >
> > amrecover still produces the same error:  Unexpected server end of file.
> >
> > I wish the debug files were more detailed.  What EOF could it be?
> >
> > Eric
> >
> > P.S.  I was in the Corps, but that is another story..
>
> Are you running on a BSD Variant?  I've found that on the server I wind up
> having to recompile with the switch --without-bsd-security in order to get
> anywhere.  Just a thought.
>
> Tony Shadwick
> Manager of Internet Services
> Strategic Technology Group
> 314-480-1324