Amanda-Users

Re: The Old Selfcheck Issue

2003-02-11 14:40:42
Subject: Re: The Old Selfcheck Issue
From: Brian Cuttler <brian AT wadsworth DOT org>
To: Brad <rbt AT vt DOT edu>
Date: Tue, 11 Feb 2003 11:11:16 -0500 (EST)
Brad,

Stupid problems I've run into.

Assuming you have both DNS and NIS/NIS+ services enabled.

/etc/nsswitch.conf (Solaris, don't know if redhat had this) wasn't
using "files" just "NIS". Check the equiv in your OS and see, also
make sure that the server information for both services are providing
the correct information, DNS has a delay window, particularly if
you are resolving against a secondary.

On my amanda systems that are clients of themselves I've always
used the IP names rather than numbers... your subnet name didn't
change with the building move ? Sometimes I include the CNAME as
well as a line for the fqdn.

Your entries are correct in .amandahosts as well as hosts.allow ?
(I'm not even sure that hosts.allow is looked at)

Sorry, not a big RH user but the concepts should port.


> Thanks to all for the help. Still no luck. I'm seeing the below libwrap
> errors in the logs. hosts.allow has entries for 127.0.0.1 and the
> localhost's fqdn, but still no go. Here is my hosts.allow file:
> 
> ALL: 127.0.0.1
> ALL: 128.173.141.0/255.255.255.0
> ALL: 128.173.203.0/255.255.255.0
> ALL: 128.173.201.0/255.255.255.0
> ALL: oubop8.bursar.vt.edu
> ALL: localhost.localdomain
> ALL: oubop8
> ALL: localhost
> 
> 
> Here are the libwrap errors:
> 
> Feb 10 13:56:45 oubop8 xinetd[1352]: libwrap refused connection to
> amandaidx from 127.0.0.1 
> Feb 10 13:56:45 oubop8 xinetd[1354]: libwrap refused connection to
> amidxtape from 127.0.0.1 
> Feb 10 13:56:45 oubop8 sshd[1356]: refused connect from 127.0.0.1
> (127.0.0.1) 
> Feb 10 13:56:45 oubop8 xinetd[1352]: libwrap refused connection to
> amandaidx from 127.0.0.1 
> Feb 10 13:56:45 oubop8 xinetd[1354]: libwrap refused connection to
> amidxtape from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1373]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1374]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1375]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1376]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1377]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1378]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1379]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1380]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1381]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1382]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1383]: libwrap refused connection to
> amanda from 127.0.0.1 
> Feb 10 13:57:10 oubop8 xinetd[1384]: libwrap refused connection to
> amanda from 127.0.0.1 
> 
> I'm seriously considering reinstalling the whole thing from scratch...
> bummer!
> 
> On Mon, 2003-02-10 at 19:56, Tim Souder wrote:
> > 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>