ERROR:Cannot resolve server "xxx" name.

[shrady]

make_net_recovery fails on a client with below error:
ERROR:Cannot resolve server "xxx" name.
Have checked /etc/nsswitch.conf, /etc/resolv.conf, /etc/hosts..everything's fine..
Please help!!!

[Steven Schweda]

> Please help!!!

You first. As usual, showing actual commands
with their actual output can be more helpful
than vague descriptions and interpretations.

> [...] "xxx" [...]

Hiding potentially important details can be
unhelpful.

> Have checked [...] everything's fine..

While your opinion may be interesting, seeing
the actual evidence which led to it might be
even more interesting. What, exactly, have
you checked, how, where?

Always a good start (on all the systems
involved):
uname -a

[shrady]

Thanks for your reply..
Below is the exact error:
ERROR: Retrieving Ignite-UX version on the server: hpignite failed.
* Creating NFS mount directories for configuration files.

======= 10/15/10 06:15:53 IST Started /opt/ignite/bin/make_net_recovery. (Fri
Oct 15 06:15:53 IST 2010)
@(#)Ignite-UX Revision C.7.10.474
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA1003/ignite/src@81040 Last Modified: 2010-04-20
15:14:50 -0600 (Tue, 20 Apr 2010)

NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x00226402FED6/recovery/defaults.

* Checking Versions of Recovery Tools
ERROR: Cannot resolve server "hpignite" name.


uname -a output at client is:
hp017:/ >uname -a
HP-UX hp017 B.11.23 U ia64 0809587682 unlimited-user license

uname -a output at server:
hpignite:/>uname -a
HP-UX hpignite B.11.11 U 9000/800 883608580 unlimited-user license

[Steven Schweda · Accepted solution]

> ERROR: Cannot resolve server "hpignite" name.

Now, on the client:
nslookup hpignite
(and so on ...)

[shrady]

hp017:/root >nslookup hpignite
Using /etc/hosts on: hp017

looking up FILES
Name: hpignite
Address: 10.19.169.160

[Pete Randall]

(like pulling teeth)

Could you also post the output of

cat /etc/resolv.conf
- and -
cat /etc/nsswitch.conf

Thanks


Pete

[shrady]

hp017:/ >cat /etc/resolv.conf
domain corp.abc.com
nameserver 10.19.164.84
nameserver 10.19.164.120

hp017:/ >cat /etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=continue] dns

[Pete Randall]

Does "ping hpignite" work?


Pete

[shrady]

Hi, yes it does ping..

hp017:/ >ping hpignite
PING hpignite: 64 byte packets
64 bytes from 10.19.169.160: icmp_seq=0. time=0. ms
64 bytes from 10.19.169.160: icmp_seq=1. time=0. ms
64 bytes from 10.19.169.160: icmp_seq=2. time=2. ms

----hpignite PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/1/2

[Chandrahasa s]

Hi,

Before configureing ignite for client you would have been created directory for image and shared.

try to mount that directory like

mount hpignite:/imgage /imgage.

is both client and server ignite version same??

Chandra

[Aneesh Mohan]

Hi,

Please try after updating hpignite entry in /etc/hosts with the below line.

10.19.169.160 hpignite hpignite.corp.abc.com

Aneesh

[shrady]

Thanks Guys! I am more than astonished to find that issue resolved when the server was backup us successfully during this week's ignite backup schedule.
I guess, it's not at all related to ignite and something from client's OS end.
Thanks again for your replies!

[shrady]

The issue, I guess, is from client's end and nothing to do with Ignite