t one reach old client. (hostname
lookup failed with the wrong IP)
oh, and the incorrect IP is actually the host address; so it's thinking
that its own IP is that of the stupid.aix.client.
So I guess actually the "stupid" server is the amanda host... :(
-Original Messa
yarlay, Wayne A.
Sent: Monday, March 13, 2006 4:45 PM
Cc: amanda-users@amanda.org
Subject: RE: New AMANDA server cannot one reach old client. (hostname
lookup failed with the wrong IP)
Thanks all for your help, Did I mention that I'm somewhat newbie-ish
with *nix? Blush. Thanks, here are my re
server cannot one reach old client. (hostname
lookup failed with the wrong IP)
On Mon, 13 Mar 2006 at 4:03pm, Matt Hyclak wrote
> On Mon, Mar 13, 2006 at 03:46:13PM -0500, Byarlay, Wayne A.
enlightened us:
>> I have a RHE4 machine with the standard AMANDA config, and then I
>>
On Mon, Mar 13, 2006 at 04:44:51PM -0500, Byarlay, Wayne A. enlightened us:
> Thanks all for your help, Did I mention that I'm somewhat newbie-ish
> with *nix? Blush. Thanks, here are my responses...
>
> 1. I did not know about this "host" command. It yields the INCORRECT
> information!
>
-
arch 13, 2006 4:08 PM
To: Matt Hyclak
Cc: amanda-users@amanda.org
Subject: Re: New AMANDA server cannot one reach old client. (hostname
lookup failed with the wrong IP)
On Mon, 13 Mar 2006 at 4:03pm, Matt Hyclak wrote
> On Mon, Mar 13, 2006 at 03:46:13PM -0500, Byarlay, Wayne A.
enlightened us
lookup failed]
Obviously I replace the true name & IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any ideas on why amanda would think that stupid.server is the wrong IP?
WAB
one! Stupid old AIX! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
Obviously I replace the true name & IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any ideas on why amanda would t
clients report OK, except one! Stupid old AIX! Amcheck
says,
ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
Obviously I replace the true name & IP with fake names.
The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
IP for this stupid.server.
Any i
one! Stupid old AIX! Amcheck
> says,
>
> ERROR: stupid.server.edu [addr 555.555.555.555: hostname lookup failed]
>
> Obviously I replace the true name & IP with fake names.
>
> The IP is NOT CORRECT! Even in the /etc/hosts file, it has the correct
> IP for this stupid
Someone have deleted the PTR record of this server. Now i have added it, and
amanda works perfectly.
I thought that was a dns problem, but i was convinced that amanda uses only
forward lookup zone.
Thanks to all for help.
Giovanni
p.s. Sorry again for bad english.
e.be
http://www.mobileware.be
"Dominique Arpin"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/07/2005 18:18
To
"Montagni, Giovanni"
<[EMAIL PROTECTED]>
cc
amanda-users@amanda.org
Subject
Re: Hostname lookup failed
> Hi to all,
> I ha
> NOTE: skipping tape-writable test
> Tape bkimmob01 label ok
> WARNING: tapecycle (20) <= runspercycle (20).
> Server check took 0.275 seconds
>
>
> Amanda Backup Client Hosts Check
> --------
> ERROR: auriga: [addr 172.30.2.195: hostname
On Mon, 2005-07-04 at 17:24 +0200, Montagni, Giovanni wrote:
> ERROR: auriga: [addr 172.30.2.195: hostname lookup failed]
Ok...
> [EMAIL PROTECTED] local]# ping auriga
> PING auriga.manord.com (172.30.2.195) 56(84) bytes of data.
Your ping test is equivalent to doing "host auriga
mob01 label ok
WARNING: tapecycle (20) <= runspercycle (20).
Server check took 0.275 seconds
Amanda Backup Client Hosts Check
ERROR: auriga: [addr 172.30.2.195: hostname lookup failed]
Client check: 1 host checked in 0.007 seconds, 1 problem found
(brought t
using
> 213721624 KB
>
> Amanda Backup Client Hosts Check
>
> ERROR: note0002: [addr 192.168.0.59: hostname lookup failed]
> Client check: 1 host checked in 10.025 seconds, 1 problem found
>
> ERROR [addr 192.168.0.59: hostname lookup
: note0002: [addr 192.168.0.59: hostname lookup failed]
Client check: 1 host checked in 10.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
In note0002 /tmp/amanda directory in amandad.*.debug files I see:
amandad: time 0.000: strange, this is not a request packet
amandad: time 0.000
: note0002: [addr 192.168.0.59: hostname lookup failed]
Client check: 1 host checked in 10.025 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
Thanks for help
Leonid
Sebastian Kösters wrote:
“amcheck DailySet1” makes the following error:
ERROR: dev2 ß CLIENT: [addr 192.168.10.1 ß GATEWAY: hostname lookup failed]
Is that funny "eszet" symbol part of the error message?
(wingdings symbol 0xDF in the html source of the mail)
Or did you make that up tog
Hi!
I got another Problem with Amanda.
“amcheck DailySet1” makes the following
error:
ERROR: dev2 ß
CLIENT: [addr 192.168.10.1 ß
GATEWAY: hostname lookup failed]
The Gateway is pingable also the Client. The Gateway
and the Client are pingable with they’re hostnames (DNS
On Fri, Apr 27, 2001 at 02:15:47PM -0500, John R. Jackson wrote:
>I think this is saying that on host samba2 it could not take IP address
>10.0.1.2 and convert that back to a host name. That IP address should
>be the IP address of the machine that connected to samba2, i.e. your
>tape server (wher
> ERROR: samba2: [addr 10.0.1.2: hostname lookup failed]
I think this is saying that on host samba2 it could not take IP address
10.0.1.2 and convert that back to a host name. That IP address should
be the IP address of the machine that connected to samba2, i.e. your
tape server (where you
This one has me a bit confused. Here are the hostnames
samba2 = 10.0.2.201
samba = 10.0.1.3
homer = 10.0.1.2
and this is the error I receive:
Amanda Backup Client Hosts Check
ERROR: samba2: [addr 10.0.1.2: hostname lookup failed
Oops!
> To disable it completely, I think you'd need to hack the source.
Obvously you don't need to but I wouldn't if I were you :-)
DSL
--
CWA - Chin Waggers Association
"Let's sit around and complain about something.
Our topic for today is: ADSL...h...that `L'
stands for Linux doesn'
Hmmm..
To disable it completely, I think you'd need to hack the source.
DSL
On Mar 13, 2001, "Charlie Zhu" <[EMAIL PROTECTED]> wrote:
> But how can I disable it, I meaning not using reverse DNS lookup?
Add it to /etc/hosts, and configure the name resolver to look up
`files' first. I.e., you don't disable it, you get it to do The Right
Thing (TM).
If you really mean to
But how can I disable it, I meaning not using reverse DNS lookup?
--Charlie
- Original Message -
From: "David Lloyd" <[EMAIL PROTECTED]>
To: "Charlie Zhu" <[EMAIL PROTECTED]>
Cc: "Amanda Users" <[EMAIL PROTECTED]>
Sent: Tuesday, March 13,
> "David" == David Lloyd <[EMAIL PROTECTED]> writes:
David> If that doesn't work, try dig 83.0.168.192.in-addr.arpa
dig -x 192.168.0.83 is less of a mouthful. :-)
Ben
Charlie!
> Amanda Backup Client Hosts Check
>
> ERROR: office: [addr 192.168.0.83: hostname lookup failed]
> Client check: 1 host checked in 0.109 seconds, 1 problem found
>
> (brought to you by Amanda 2.4.2)
>
> But 'office'
Hi all,
I encounter following error from my CNCBACK in 192.168.0.83
[root@CNCBACK DailySet1]# su backup -c "amcheck DailySet1 -c"
Amanda Backup Client Hosts Check
ERROR: office: [addr 192.168.0.83: hostname lookup failed]
Client check: 1 host checke
>Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
For starters, it should state that the error is coming from the client, not
from amcheck on the tape server. Something like:
"Client-side error: unable to perform reverse lookup on ".
Ben
>Is it possible that the error message could be improved?
Sure. Do you have a suggestion?
I'm not sure what 2.5 will say about this. The new security framework
has significantly altered the flow in this area.
>Ben
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
It says that when Amanda tried to do a reverse lookup (IP
203.24.38.228 back to a host name), it failed.
Ahh. Problem sorted, thanks. Name service had died at that machine's site.
Is it possible that the error message could be improved?
Being able to ping the host is irrelevant. I as
>ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
FYI, this is reported from the client side, so you need to do your
testing there, not on the server.
>This is nonsense -- I can ping the host, so my resolver is not broken.
>What else can cause this?
It says that when Amanda
I just got a note from amcheck about a problem with one of my client
workstations:
Amanda Backup Client Hosts Check
ERROR: metro: [addr 203.24.38.228: hostname lookup failed]
Client check: 5 hosts checked in 1.692 seconds, 1 problem found
This is nonsense -- I
richard wrote:
>
> My /var/named/rev.38.164.85.202 file is:
> @ IN SOA ns31.newsbook.net. ns31.newsbook.net. (
> 1997022700 ; serial
^^
Did you change the serial number after any changes you made to the file?
--
Re
richard wrote:
>
> Dear all,
> Thanks for your hint. But I have checked the following and the problem
> still exists.
> After the ./amdump, I still get the error:
> FAILURE AND STRANGE DUMP SUMMARY:
> 202.85.165 /home lev 0 FAILED [202.85.165.88: [addr 202.85.164.38
>My /etc/resolv.conf:
>domain ns31.newsbook.net
>search ns31.newsbook.net
Here you are saying that your domain is ns31.newsbook.net.
Is that what you want?
- Peter
--
Peter N. M. Hansteen [EMAIL PROTECTED] http://www.datadok.no
Datadokumentasjon A/S, Bredsgaarden 2, N-5003 Bergen, Norway
T
Dear all,
Thanks for your hint. But I have checked the following and the problem
still exists.
After the ./amdump, I still get the error:
FAILURE AND STRANGE DUMP SUMMARY:
202.85.165 /home lev 0 FAILED [202.85.165.88: [addr 202.85.164.38:
hostname
lookup failed]
Can anyone tell me what is
> richard wrote:
>
> *** Default servers are not available
>
Do you have a DNS server? It seems that you don't. If you really don't
have one, then you should update your /etc/hosts file (or, more
precisely, whichever alternative to DNS is listed in your
/etc/nsswitch.conf file in the entry "hos
>*** Default servers are not available
The machines which amanda thinks are the default name servers for
your domain are for some reason not responding, it seems. Check
your resolv.conf.
--
Peter N. M. Hansteen [EMAIL PROTECTED] http://www.datadok.no
Datadokumentasjon A/S, Bredsgaarden 2
--ERROR: 202.85.165.88: [addr
202.85.164.38: hostname lookup failed]Client check: 2 hosts checked in 0.023
seconds, 1 problem found.
(brought to you by Amanda 2.4.1p1)
And have the above problem. So, I use nslookup in my server
and get:
[root@ns31 DailySet1]# nslookup*** Ca
>Date: Thu, 16 Nov 2000 13:24:52 -0600 (CST)
>From: Joi Ellis <[EMAIL PROTECTED]>
>>I'm pretty sure that all (UNIX) versions of nslookup uses gethostbyname();
>>...
>I'm not sure of this at all. On our internal machines, various breeds
>of linux and solaris, nslookup doesn't return an answer if
>Ok, i will test this. But, did nslookup not use them ?
No, I don't think nslookup uses gethostby*. I've always been under the
impression nslookup only does DNS queries, which are the layer below
the gethostby* routines. I wouldn't, for instance, use it to debug an
NIS problem.
It's entirely p
On Thu, 16 Nov 2000, David Wolfskill wrote:
>I'm pretty sure that all (UNIX) versions of nslookup uses gethostbyname();
>I'm less confident about their use of gethostbyaddr(). (I'm pretty sure
>that there have been some versions of nslookup that would try to do a
>gethostbyname() using an IP add
>From: Thorsten Flick <[EMAIL PROTECTED]>
>Date: Thu, 16 Nov 2000 16:37:49 +0100
>DNS is running well. and i administer it for myself.
Good -- reducing the effects of "middlemen" helps get work done. :-}
>> [stuff about gethostbyname() & gethostbyaddr()...]
>Ok, i will test this. But, did ns
> >Amanda Backup Client Hosts Check
> >
> >ERROR: intranet: [addr 192.168.1.42: hostname lookup failed]
> >Client check: 3 hosts checked in 0.318 seconds, 1 problem found.
> >-
> >Server and Client are running the same Ser
: intranet: [addr 192.168.1.42: hostname lookup failed]
>Client check: 3 hosts checked in 0.318 seconds, 1 problem found.
>(brought to you by Amanda 2.4.1p1)
>-
>Server and Client are running the same Server-Version.
OK; so fix the DNS (or whatever alternative hostname resolutio
Hi there,
i have a new Problem if i want to include another host in my backup.
amcheck says the following :
--
Amanda Backup Client Hosts Check
ERROR: intranet: [addr 192.168.1.42: hostname lookup failed]
Client check: 3 hosts checked in 0.318 seconds, 1
48 matches
Mail list logo
