>If I do amrecover on the command line,
># amrecover
>...
>amrecover: Unexpected server end of file
If you look at /tmp/amanda/amindexd*debug on the server you'll probably
see that it tried to set the configuration to whatever default you
built in at ./configure time, and that configuration does not exist.
I think I have a TODO item to report that back to amrecover.
>No index records for disk for specified date
>... I have index generation enabled too and there are files created
>in my index dir.
Well, amindexd wasn't happy with them. Does "amcheck -l Daily" run as
the Amanda user have anything interesting to say about them?
Are you sure the permissions and ownerships are correct for indexdir
(from amanda.conf) and all the subdirectories and files?
What files are in the "_var" directory at the bottom?
If you zcat the most recent level 0 index into "head", what do the
first few lines look like?
>service amanda
>{
>...
You may want to add "groups = yes" so amandad gets any alternate groups.
>service amidxtape
>{
>...
>server_args = amidxtaped
Get rid of that "server_args" entry. None of the Amanda services expect
to get command line args when they are started, and some get very upset.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
