Should be fixed in Ubuntu 12.04 after moving to Upstart.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nis (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: autofs (Ubuntu)
Status: Confirmed => Fix Released
--
You received
Is anyone still having this problem in Ubuntu 12.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50430
Title:
NIS has problems starting before the network comes up
To manage notifications about t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50430
Title
Solution suggested by gwir above does not solve the problem on Natty 11.04.
I still need to restart autofs by hand to get access to my NFS remote home
directories and so to my Ubuntu desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Hello,
This is the script i'm using :
/etc/network/if-up.d/net_is_configured :
#!/bin/sh
# Testing if network is up before continuing
network=`route -n | sed -ne '/^224/d' -e '/^127/d' -e '/^[0-9]/p'`;
timeout=0
while [ "${network}" = "" ] && [ ${timeout} -le 20 ]
do network=`route -n |
Here's what I use. This works for me in 10.04 (and below) but I haven't
tried it with 10.10 yet.
It sure as heck would be nice if someone paid a little attention to this
bug.
Save this as "reautofs", then follow the directions in the comments.
#!/bin/sh
#
# Stupid NetworkManager doesn't wait fo
got a really ugly fix that make nis finally working... at this to your
/etc/rc.local :
while [ ! "`/bin/pidof ypbind`" ]
do
/etc/init.d/nis restart
sleep 2
done
exit 0
that should do it!
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You re
NetworkManager can't be uninstalled without uninstalling "ubuntu-
desktop" as well :-(.
Filed bug 503264 about that.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I will second the recommendation to remove network-manager...I also
have had success in earlier revs of ubuntu
in re-ordering the startup scripts so that NIS starts before autofs...
dont remember if I had to do that in Karmic or not.
This problem has been around a while now on various ubunt
Johan, unless you use NIS on an laptop I recommend to deinstall network-manager
and use the old style /etc/interfaces configuration. At least this works for
me. Don't have the respective machine at hand right now, so I'm not 100% sure
if it is karmic already but I positively think so.
g., fil
Has anybody managed to work around this on Karmic?
I just upgraded to Karmic, and my previous workaround is no good any
more, and I now have to (re)start NIS manually at each boot :-(.
Also, the top of the bug page says "This bug affects you and one other
person". Considering the amount of peopl
System | Administration | Services
That's all nice and good, but with the conversion to Upstart in karmic,
this doesn't apply anymore. Anyone have a more "karmic" solution?
Sean
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this b
The workaround for this is well known but is not really explained
anywhere in any one place; there are comments on all the bugs related to
this one (especially 354588) and also in the Ubuntu forums. What is
comes down to is the ordering of startup of NIS and NetworkManager. If
NetworkManager is a
vagr...@vagrant-laptop:/etc/init.d$ sudo /etc/init.d/nis start
sudo: unable to resolve host vagrant-laptop
* Starting NIS services
* binding to YP server...
*
** Changed in: autofs (Ubuntu)
Status: Incomplete => Confirmed
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Chuck,
This seems to be working, but my box isnt a super clean test - its had
upgrades from earlier revs and I cant
remember if I moved the /etc/rc2.d startup script #'s around... can you
tell if this is the stock order of init scripts?
tes...@lucky:/etc/rc2.d$ ls -la
total 20
drwxr-xr-x 2 ro
Hi,
I was wondering if this is still a problem on karmic?
Regards
chuck
** Changed in: autofs (Ubuntu)
Importance: Undecided => Low
** Changed in: autofs (Ubuntu)
Status: New => Incomplete
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
@Paul: I can confirm the problem with nis and NM on Ubuntu Jaunty so I
don't think that problem is already solved.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
S28NetworkManager simply requires that networkmanager be started. That
does NOT guarantee that you have an active network connection. The
whole idea behind NM is that it will manage network connection and
disconnect for the system, behind the scenes.
What's happening here is that NM comes up and
> Is this still the case even with "System setting" (renamed to "Available to
> all users" in jaunty) and "Connect automatically" both checked?
Yes. In my case it isn't NIS that's affected however, but rather my
network mounts which are run from rc.local. They never work at boot
(and if I log th
Is this still the case even with "System setting" (renamed to "Available to
all users" in jaunty) and "Connect automatically" both checked?
On Tue, May 19, 2009 at 2:19 PM, Alex F wrote:
> It seems like the problem is NetworkManager botching its role in the
> boot process. It's supposed to brin
It seems like the problem is NetworkManager botching its role in the
boot process. It's supposed to bring the network up at S28, but
starting almost three years ago with this bug and yet today on a fresh
9.04 install, the network is not even up by S99 for rc.local.
Can NetworkManager please be fi
or, solution #4
* add some package "legacy-network" or the like, that re-introduces
/etc/network/interfaces config. Let nis, autofs and the like depend on this
one. Traditional unix concepts require having network up early. Don't twist
them all, instead satisfy their need.
--
NIS has problems
** Also affects: autofs (Ubuntu)
Importance: Undecided
Status: New
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Same old problem on a fresh 9.04.
It boils down to: ypbind is tried at S18nis, NetworkManager starts a lot
later at S28NetworkManager. IP connectivity often isn't up after S99, at
least if using DHCP.
The problem disappears after configuring the old way via
/etc/network/interfaces , thereby shor
Apparently, the problem is not limited to NIS, but if there is no user
logged with the greeter, none of the network services (i.e. ssh, nfs)
seems to run properly.
Call it "feature", but I consider it a critical bug, since activating
the network manually with the init.d commands doesn't help.
Thi
Addenda: forgot to mention, I'm running Ibex with both default kernel
and default installation.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that after 2.5 years, we are no nearer having NIS work properly
during boot. Intrepid tries 11 times to start NIS and fails -- this
takes up a long time, trippling or quadrupling boot times.
Once booted NIS appears to be working fine.
Assuming you are on a laptop and not a workstation,
If you use NIS-distributed autofs maps, you need to restart autofs as
well - *after* you've restarted NIS.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I know this isn't specifically a NIS problem, as someone has already
mentioned, but the NIS issue causes auto logins to fail. Johan's hack
appears to fix it for me (thanks, Johan).
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bu
I too can confirm the problem.
Hardy 64
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I just upgraded to Hardy (on a new machine, so settings might have
changed), and the workaround in comment 14 does not work for me any
more.
However, putting an executable file with the following contents in
/etc/network/if-up.d works:
"
#!/bin/sh
invoke-rc.d --quiet nis restart &
"
--
NIS has
I too can confirm the problem. nis starts before network is fully up and
times out. It would be great if this bug is fixed and the functionality
works out of the box without having to remove network manager.
I also have a problem with automounter not mounting my home directory. I
had to create my
I can confirm this bug still exists in hardy, and the workaround of
removing network-manager does fix it.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
If you have a stationary workstation setup, with NIS, autofs, fixed IP
numbers etc. you are better off removing network-manager altogether.
I've had several of the problems above, and they magically disappeared
when I did this:
apt-get remove network-manager
It removes a number of GUIs as well,
Hi,
I just upgraded to gutsy and this annoying bug has also bitten me.
Fortunately I found a simple workaround somewhere else (can't remember
where =( ) that worked for me, and only messes with the real culprit
AFAICS: if you disable NetworkManager's "roaming mode" and force
"Automatic configurati
Dag-Erling: It looks like you're right and Network Manager is confused
on your system. Even in the last entry in the log you have there it
reports:
| State: connecting
rather than reporting that it is in the connected state. The ypbind code
triggers on the connected state so if Network Manager is
See the attached log. The first ten or so instances are from
/etc/init.d/nis in the normal startup sequence. The second-to-last
instance is from the beginning of /etc/rc.local. The final instance is
from /etc/rc.local immediately before /etc/init.d/nis is run again
(successfully).
Note that ypb
Dag-Erling: The point here is that the Network Manager integration in
NIS (which is disabled by default) is supposed to work around these
issues by doing something very similar to what the script fragment you
posted does. This means that NIS is affected by only a subset of the
problems that affect
Mark, I'm running nis 3.17-2ubuntu2. You have my config file, feel free
to have a look. I am having problems.
I *think* this violates your hypothesis. Please clarify if you think
otherwise.
Regards //Johan
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/
One thing that just occurred to me, could this be caused by
interoperability issues between NetworkManager and the specific NIC
driver being used (tg3 in my case), as in this report of a similar
problem which was fixed by switching drivers: https://bugs.launchpad.net
/network-manager/+bug/38586
--
Once again, this is *not* a NIS problem, it is a NetworkManager problem
that affects far more than NIS. I do not have -no-dbus in
/etc/default/nis.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a m
If it's not explicitly disabled and you're running version 3.17-1 or
later then it is enabled - if Network Manager is running then ypbind
should pay attention to it.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification b
Attached my /etc/default/nis. It doesn't say anything about Network
Manager integration. No options seem to be passed to ypbind AFAICT.
Mark, how do I edit it to ensure Network Manager integration is enabled?
** Attachment added: "nis"
http://launchpadlibrarian.net/8836011/nis
--
NIS has
In the case of NIS all you need to do is edit /etc/default/nis to ensure
that Network Manager integration is enabled (make sure the -no-dbus
option isn't being passed to ypbind). If it still fails after that then
there's a problem with Network Manager. With Network Manager integration
enabled ypbin
The NIS failure is obviously highly visible since it does not fail
gracefully (i.e. it will not magically fix itself once the network is
up) and it prevents you from logging in, but this is not just a NIS
issue; it affects anything that requires a working network connection
and / or DNS to start (N
It's funny. The same problem exists on Mac OS X Tiger: ypbind starts
before the system received an IP from DHCP. Now Ubuntu joins the crowd.
I put the following in /etc/network/interfaces:
auto eth1
iface eth1 inet dhcp
up /etc/init.d/nis restart
This seems to help sometimes.
--
NIS has proble
** Summary changed:
- nis client seems to not start at boot
+ NIS has problems starting before the network comes up
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is
49 matches
Mail list logo
