>Upgraded Amanda yesterday from 2.4.1p1 to 2.4.2p2 ...
>amcheck runs successfully.
>
>Any idea why there is a failure in the amdump ?
>...
> bali /usr5 lev 0 FAILED [bali: [hostnames do not match: bali bali.wads
>worth.org]
I'm surprised amcheck didn't fail. This message comes from amandad
which they both use.
Here's what happened:
* amandad took the IP address of the machine connecting to it and
converted that to a host name with gethostbyaddr. It got back "bali".
* It took that name and did a host name lookout with gethostbyname.
It got back "bali.wadsworth.org".
Looks like you have a host name lookup problem.
There are a couple of trivial test programs at:
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c
They use the exact same call Amanda uses. You cannot trust grepping
through /etc/hosts or running nslookup. Those depend on how your system
is configured to do lookups.
> sicily /usr1 lev 0 FAILED [disk /usr1 offline on sicily?]
> sicily /dev/root lev 0 FAILED [disk /dev/root offline on sicily?]
> sylt /usr7 lev 0 FAILED [disk /usr7 offline on sylt?]
> sylt /usr4 lev 0 FAILED [disk /usr4 offline on sylt?]
> sylt /dev/root lev 0 FAILED [disk /dev/root offline on sylt?]
If amcheck did not complain about these, the next thing to look at is
the /tmp/amanda/sendsize*debug file. In particular, look at the first
and last lines and see how long the estimates took. You may need to
crank up etimeout in amanda.conf.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
