>When I run amcheck I get 'selfcheck request timed out' while trying to
>connect to localhost ...
First, don't use "localhost". It will bite you eventually. Use the
fully qualified domain name of the host. Any modern network code will
notice they are the same thing and you won't lose any performance.
>I remember getting this error on other installations. It seems to get
>me every time I do a new install or even an update on an old machine.
It is, by far, the most common problem for new installations. There are
just so many OS's and possible ways for to screw up, that unless you
practice all the time :-), it's probably going to keep showing up.
>... I
>have found that with a machine with two ethernet interfaces, each with
>its own IP and name, one will work and the other will fail. ...
If you get a case like this again, please post and maybe we can look
into what's going on and see if there is something Amanda could do to
make it better.
>I have
>found cases where I need to put both the user and the operator in
>inetd.conf.
Not sure I understood this one.
>Does anyone have a complete list of what causes this error message? ...
That's what the FAQ at www.amanda.org is for. Here are the main URL's
about this particular topic:
http://amanda.sourceforge.net/fom-serve/cache/16.html
http://amanda.sourceforge.net/fom-serve/cache/140.html
I think some of this is also covered in "the book chapter" referenced
at www.amanda.org.
>... I
>keep thinking about what it could be and then I try something. If it
>fixes it I stop (and forget exactly what I did to get it working). ...
Instead of forgetting :-), how about adding an FAQ item yourself?
You'll not only help yourself next time you run into the same thing,
you'll also be helping other people.
>Josh Kuperman
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
