That's the bitch of it...it IS resolved: via nslookup, via ping--ANYTHING but Amanda.

It's bizarre.  I'm getting ready to compile amanda from source to see if it's a 
problem with the rpm on the client.  Rpm installs are OK sometimes--other times, I'd 
rather not deal with 'em.

anyone else wanna take a stab at this?

thanks anyways,

bryan

======================================== 
Bryan S. Sampsel
Systems Administrator
Ambeo, Inc.
========================================

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bort, Paul
Sent: Tuesday, June 12, 2001 3:04 PM
To: 'Bryan S. Sampsel'; [EMAIL PROTECTED]
Subject: RE: Try2, Amanda Question


The problem being reported is that redhat2.pine-cone.com can't resolve the
address 172.16.3.1. Either add it to your local DNS, or /etc/hosts. 


> -----Original Message-----
> From: Bryan S. Sampsel [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 4:02 PM
> To: [EMAIL PROTECTED]
> Subject: Try2, Amanda Question
> 
> 
> 
> the first time never got to the list, unless there's a 
> massive delay...so here we go again.
> 
> I have Amanda server running on a RedHat 7.1 system with an 
> HP4mm DAT.  works fine when I back up a solaris client.
> 
> However, when I try to back up a dns-resolved client (a 
> RedHat 7.0 system, same Amanda rev as the Amanda server), I get:
> 
> ====
> Amanda Backup Client Hosts Check
> --------------------------------
> ERROR: redhat2.pine-cone.com: [addr 172.16.3.1: hostname 
> lookup failed]
> Client check: 1 host checked in 0.052 seconds, 1 problem found
> 
> (brought to you by Amanda 2.4.2p2)
> 
> ====
> 
> DNS works, I even added the client to the /etc/hosts file.  I 
> can ping by name from the account.
> 
> I ran the amcheck from the Redhat 7.0 client and it all checked out.
> 
> Any ideas?
> 
> thank you for ANY assistance or ideas,
> 
> bryan
> 
> ======================================== 
> Bryan S. Sampsel
> Systems Administrator
> Ambeo, Inc.
> ========================================
> 

Reply via email to