On Thu, Apr 16, 2009 at 09:45:10PM -0400, Gordon Ross wrote:
> I'm still having this problem after every reboot.
> Here's some more information.  During starup, this svc fails:
>   svc:/network/routing/ndp:default
>
> The start method eventually gets killed by SMF for
> taking so long to complete.  It's running:
>   /usr/lib/inet/in.ndpd
>
> I tried running that by hand, with the -d option,
> and I observe that it seems to be trying to do an
> IPv6 DHCP on my wired interface, and just waits...
> (I'll send the log once I get that machine back up)
>
> After this service goes into maintenance,
> nwam doesn't start either.  (a dependent?)

What do you mean by "nwam doesn't start"?  Is the service in
maintenance?  Enabled but offline?

network/physical:nwam does not depend on ndp; rather, ndp
(indirectly) depends on network/physical (either the default
or nwam instance will satisfy the dependency).  That is, ndp
depends on milestone/network, which depends on network/physical.

So if nwam is in a funky state, that could be contributing to
the ndp weirdness (though I would expect more than just ndp to
be unhappy in that case).  Or maybe something else is making both
serices unhappy.

If it seems that nwam has run amok, enabling debugging and getting
a log of what it does on boot would be helpful.  Please refer to
http://opensolaris.org/os/project/nwam/picea/troubleshooting/; the
last note on that page ("None of the above") describes how to enable
debugging.

Thanks,
renee

> I haven't a clue what's going on here.
> Any suggestions?
>
>
>
> On Apr 9, 2009, at 8:14 AM, OpenSolaris Forums wrote:
>
>> About a week ago, I upgraded to snv_111.  Suddenly yesterday and  
>> today,
>> the machine does not bring up a network at boot.  I'm using nwam.
>>
>> # svcs -vx
>> svc:/network/routing/ndp:default (in.ndpd IPv6 neighbour discovery  
>> daemon)
>> State: maintenance since ...
>>
>> And in the log file:
>> Executing start method ("/lib/svc/method/svc-ndp)
>> Method or service exit timed out.  Killing contract 100
>> Method "start" failed due to signal KILL
>>
>> ifconfig -a shows me three interfaces: iwk0, bge0, vboxnet0
>> The latter two show inet6 addresses.
>>
>> I don't remember enabling IPv6 on this machine,
>> but apparentl it is now, and it ain't work'in!
>>
>> Help!
>>
>> Thanks,
>> Gordon
>> -- 
>> This message posted from opensolaris.org
>> _______________________________________________
>> networking-discuss mailing list
>> [email protected]
>
> _______________________________________________
> networking-discuss mailing list
> [email protected]
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to