Re: amrecover: Unexpected server end of file

[John R. Jackson]

>In the client:
>...

OK.  You don't need amandaidx or amidxtape on a client, but they are
probably not hurting anything.

>In the server:
>...

OK, so inetd/xinetd is listening.

>There isn't any amindexd*debug in the server.

The inetd/xinetd is having trouble starting it.

Are there any system log messages from inetd/xinetd when you try to
connect?  Like something about the service failing or looping?

What happens if you run amindexd yourself as the Amanda user.  Add the
"-t" command line option so it knows to run interactively.  Just enter
a Ctrl-D or "QUIT" to make it go away.

Does the /tmp/amanda/amindexd*debug file get updated for this?

What does your inetd/xinetd config line/file look like?

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]