Jesper, are you still seeing this problem?
** Summary changed:
- nis client fails to start at bootup
+ Can't cope with Network Manager stopping
--
Can't cope with Network Manager stopping
https://bugs.launchpad.net/bugs/105648
You received this bug notification because you are a member of
Ah, this looks like Network Manager is crashing or otherwise stopping at
some point after ypbind has started. The ypbind code can't cope with
that - it assumes that if Network Manager is running at startup it
should continue to rely on it. You should be able to check this by
running ypbind in
Could you please have a look in /var/log/syslog and see if you see
messages along these lines:
Feb 1 08:32:39 localhost ypbind: Host name lookup failure
there? Thanks.
--
nis client fails to start at bootup
https://bugs.launchpad.net/bugs/105648
You received this bug notification because you
There is no log-messages about ypbind in syslog (neither when it tries
to start during bootup or when it is started subsequently)
--
nis client fails to start at bootup
https://bugs.launchpad.net/bugs/105648
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
OK, it's not a duplicate of a previous bug with similar symptons. Could
you please provide any output that is produced (either in syslog or via
the init script) as well as the output of running 'nm-tool'?
Thanks.
--
nis client fails to start at bootup
https://bugs.launchpad.net/bugs/105648
You
Strange.. Now I removed it from rc.local and it works fine. It must somehow be
related to the other stuff of configuration on the system and/or the packages
updated during the last 24 hours in feisty. It works now.
$ nm-tool
NetworkManager Tool
State: connected
print_devices(): didn't get a
Ok.. bug found .. but no soloution.
The problem only occours when an dhcp-adresse is assigned. Then does
# nm-tool
NetworkManager Tool
get_nm_state(): didn't get a reply from NetworkManager.
NetworkManager appears not to be running (could not get its state).
instead of in the above
