Re: "route" problem
From: Andrew Gabriel (andrew_at_cucumber.demon.co.uk)
Date: 01/30/05
- Next message: Strikz: "Re: "route" problem"
- Previous message: Bridge: "Xsun process using CPU time"
- In reply to: Barry Margolin: "Re: "route" problem"
- Next in thread: Strikz: "Re: "route" problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 30 Jan 2005 19:06:16 GMT
In article <barmar-EC25A8.09140930012005@comcast.dca.giganews.com>,
Barry Margolin <barmar@alum.mit.edu> writes:
> In article <1107092032.474519.146650@f14g2000cwb.googlegroups.com>,
> "Strikz" <dejanews@strikz.co.uk> wrote:
>
>> Hi,
>>
>> I've a main Solaris 8 NIS server that until recently was running fine,
>> but it hadn't been rebooted in several months. It lost power, and when
>> I recovered it I found it freezes on boot-up.
>>
>> I was able to get into single user mode, and add a set -x to the
>> inetinit script. As the machine normally boots it runs inetinit and
>> during that script the "route" command is run to add the default
>> gateway. This is where apparently the machine halts.
>>
>> If I remove defaultrouter, then on boot the machine does come all the
>> way up. I can access the server from the same subnet, but not from
>> others (obviously). If I then manually run the route command, it halts
>> that telnet session (I'm not able to CTRL-C out). The "route" binary
>> looks ok, FILE tells me its a sparc binary. I also think all the lib
>> files required are ok too.
>>
>> A colleague of mine thinks the route program is waiting on the network
>> to respond with something that its not getting. But all of the NIS
>
> Route doesn't normally send anything over the network, unless you give
> it a hostname rather than an IP address, in which case it may have to
> use NIS or DNS to resolve the name. But that shouldn't cause an
> unkillable hang.
>
>> clients use the same gateway and they all boot-up fine.
>> Any idea how I can diagnose this more? Or what might be going on?
>
> Not sure, but to narrow it down further, try running:
>
> truss route add default ....
>
> to see what system call it's hanging in.
I wonder if an incorrect route command is blackholing the
packets (at least the telnet ones over which the command
was issued)?
Kind of sawing off the branch you're sitting on ;-)
-- Andrew Gabriel Consultant Software Engineer
- Next message: Strikz: "Re: "route" problem"
- Previous message: Bridge: "Xsun process using CPU time"
- In reply to: Barry Margolin: "Re: "route" problem"
- Next in thread: Strikz: "Re: "route" problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
