Amanda-Users

Re: The Old Selfcheck Issue

2003-02-10 21:14:29
Subject: Re: The Old Selfcheck Issue
From: Tim Souder <tsouder AT mcs.drexel DOT edu>
To: Brad <rbt AT vt DOT edu>
Date: Mon, 10 Feb 2003 19:56:40 -0500 (EST)
Also, just to be sure, check to see if the new name of the host (which
may have changed if the host uses dhcp to grab its name) is setup properly
in the disklist file (of course, if the name of the backup server is
localhost in disklist this cannot be a problem).

I hope this helps,

Tim

On 10 Feb 2003, Brad wrote:

> Hello,
>
>
> We change the IP address on our amanda server because we moved to a new
> building. Now, when we run "su amanda -c "amcheck daily" we continually
> get the 'selfcheck request timed out' error, but the server can still
> check the other hosts it backs up. No other changes were made to the
> server. It was up and running for several months before the move w/o any
> problems. Here's what I've verified:
>
> amanda can write to /var/tmp/amanda
> there are no firewalls in place
> according to lsof, all amanda services are still running
> I can ping the server from itself and from other clients on the network
> Restarting xinetd or rebooting does not correct the problem
> The server has entries for itself in /var/lib/amanda/.amandahosts
>
> Any ideas? We're using version 2.4.2p2-7 on a RH 7.3 server (it was
> installed with RH's default rpms). Like I said earlier, it worked
> perfectly for several months before we moved to the new building and
> changed IPs, but that doesn't seem like it should cause this.
>
> Thanks
>
>


<Prev in Thread] Current Thread [Next in Thread>