On Thu, Jul 27, 2006 at 09:16:36PM -0500, Mark Griffith wrote:
> Pavel,
> 
> I think, I did this before, but here goes...
> 
> amrecover gssserv -s gssserv  -t gssserv
> AMRECOVER Version 2.4.4p4. Contacting server on gssserv ...
> 501 Could not read config file /usr/local/etc/amanda/#/amanda.conf!
> 
> Starting to get annoying.

That message "Could not read config ..." comes from a function
in amindexd.c "is_config_valid(configname)".  I don't think
you would get that far if you hadn't connected correctly.

However, it appears that the configname it is looking at is "#" !!!
Why I don't know.

On your server, is /usr/local/etc/amanda the directory holding
your config directories?  I.e. is it looking in the right place
but for the wrong name?  I presume the correct config name is
gssserv.

Gee, if it is the correct directory path I wonder if a workaround
would be to run " ln -s ./gssserv /usr/local/etc/amanda/# "

Is the default config on your client "#"?  Just trying to guess
where the "#" is coming from.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)