Re: [Networker] No response from client

2004-12-03 14:07:16
Subject: Re: [Networker] No response from client
From: Darren Dunham <ddunham AT TAOS DOT COM>
Date: Fri, 3 Dec 2004 11:06:22 -0800
> 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 com
Senior Technical Consultant         TAOS  
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 where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu