Re: [Networker] No response from client
No, but here's what I discovered. The wrong ip was listed in the
client's /etc/hosts. The correct host name was listed but with the wrong
ip. The DNS, however, lists the correct one. This wrong ip address is
also the one that was showing up in the output from the strace command,
and it appears twice in the /nsr/res/nsrla.res file after two resource
resource identifier: 4.#.###.#.###.###.###.##.IP-ADRESS(61)
resource identifier: 6.#.###.#.###.###.###.##.IP-ADRESS(1)
With the exception of the first digit, and the numbers in parenthesis,
everything else on both lines is identical.
I should also note that /etc/nsswitch.conf uses the order: files nis dns
for hosts. I changed the ip address in the client's /etc/hosts file to
the correct value (no reboot) and EVERYTHING works now! I can also run
the GUI tools and command line tools like mminfo, and they no longer
hang. I guess prior to the fix, the host at some point would get around
this hurdle and finally back itself up but it would take a long time.
Probably eventually timed out and used NIS or DNS but might bounce
aroudn a long time?
How should I correct the wrong entries in nsrla.res? Can I manually fix
that or is there a better way? Also, is it necessary? What do those
preceeding numbers before the IP indicate?
Darren Dunham wrote:
> > sin_addr=inet_addr("##.##.###.###")}}, 16
> > It hangs right at the ", 16"
> > I substituted '#' for the actual ip address that was shown. I should
> > note that this is the ONLY ip address listed in the output, AND it's not
> > the client's ip, the storage node or the primary server's ip. Oddly,
> > it's some other machine that has no connection with backups whatsoever
> > and is currently unreachable by ping. In fact, I think it's powered off.
> > When I run 'strace -o /tmp/foo savefs -p' on another host (one that's
> > acting normally), I see three different ip addresses listed: primary
> > server (many times), client (once), and the machine that the client is
> > ypbound to (many times). Not sure if that's any relation to why it shows
> > up in the output since it has no direct affiliation with the backups
> > (it's not a storage node server or anything), but from what I can
> > observe, the only IP address that's showing up in the output that I get
> > on this weird host is an ip for a host that's not even alive.
> Is the IP in /etc/hosts? Does that IP or name exist anywhere within the
> files in /nsr/res on the client?
> It's obviously doing something with the address and then timing out.
> Darren Dunham ddunham AT taos DOT
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu