>I recently decided to add another Amanda client to my existing Amanda
>setup (server running v2.4.1p1) where I back up three clients using Krb4.
Does the new client also use Krb4?
>ERROR: shell1.nominum.com: couldn't resolve hostname
Here's the relevant code:
#ifdef KRB4_SECURITY
if(hostp->disks->auth == AUTH_KRB4)
rc = make_krb_request(hostp->hostname, kamanda_port, req,
hostp, CHECK_TIMEOUT, handle_response);
else
#endif
rc = make_request(hostp->hostname, amanda_port, req,
hostp, CHECK_TIMEOUT, handle_response);
req = NULL; /* do not own this any more */
if(rc) {
/* couldn't resolve hostname */
fprintf(outf,
"ERROR: %s: couldn't resolve hostname\n", hostp->hostname);
So what the message really means is that make_krb_request (if you're
using krb4) or make_request sent back a non-zero return code.
It's true that a simple make_request call can only return non-zero if
gethostbyname fails.
However, make_krb_request can fail if either host2krbname fails or if
add_krb_security fails. Host2krbname can only fail if gethostbyname
fails, so we're back to the ability of the Amanda server to be able to
look up shell1.nominum.com (see below).
Add_krb_security calls get_krb_security which can fail if krb_mk_req
(which appears to be a low level K4 routine?) fails. For that it's
working with CLIENT_HOST_PRINCIPLE, CLIENT_HOST_INSTANCE, the realm and
the incoming request.
The first thing I'd do is make sure gethostbyname works for that client.
I'd do that with:
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c
You cannot trust nslookup to give you the right answer -- it only tests
DNS, not the other possible host name sources (e.g. /etc/hosts).
If none of that helps, I'd start stepping through the K4 code and see what
it didn't like and (hopefully) why. But K4 is only minimally supported in
Amanda, and I certainly don't know much about it other than the basics.
I'm just hoping the above overview will jog some memory of what you did
on one of the other clients that does work.
Clearly that message should be cleaned up a bit. I've added that to the
TODO list.
>Thanks - Peter
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
