! 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 think
the 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 ideas
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 think
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
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:
I have a RHE4
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!
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
copied over my amanda.conf
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 responses...
1. I did
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 Message-
From: [EMAIL PROTECTED
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.
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 to you
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. What Amanda
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 lookup failed]
Client check: 1 host checked in 0.007 seconds, 1 problem found
Verify
://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 have a problem with amanda.
In december i've set-up amanda
: 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
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 failed]
192.168.0.59 is my amanda server IP
: 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
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 theyre hostnames (DNS). I also
Sebastian Ksters 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 together
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 ran
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 (where
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
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' is really pingable in fact,
What does
"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
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, 2001 1:56 PM
Subje
Hmmm..
To disable it completely, I think you'd need to hack the source.
DSL
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
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
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 tried to do
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 IP".
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
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:
hostname
lookup failed
*** 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
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
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 nslookup
35 matches
Mail list logo
