Removing network-manager and dependencies resolves this issue.
NetworkManager seems to let the system continue booting before the
network is completely ready. Removing it cures it.
--
nis client seems to not start at boot
https://bugs.launchpad.net/bugs/50430
You received this bug notification be
I am also encountering this issue on a fresh Feisty install. Restarting
NIS resolves the issue.
--
nis client seems to not start at boot
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
Assuming I'm seeing the same problem as the original reporter, yes.
What happens during my boot sequence is (in order):
* network manager starts trying to get a dhcp address
* /etc/init.d/nis attempts to start but fails because the network isn't up
* network manager manages to get a DHCP address a
Is the bug still present in Feisty?
** Changed in: nis (Ubuntu)
Assignee: (unassigned) => gmlion
Status: Unconfirmed => Needs Info
--
nis client seems to not start at boot
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs
It's probably not localhost that cannot be looked up, thats just the format of
the syslog(3) message. Here's the full line from my /var/log/user.log.0:
"
Feb 1 08:32:39 localhost ypbind: Host name lookup failure
"
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
u
If it can't resolve localhost that suggests some other problem: it ought
to be able to do that without the network.
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
I *think* I'm having the same problem.
For some reason my network card is slow at coming up. Because of that,
"/etc/init.d/nis start" gets run before the network is up. Then ypbind
gives up with "localhost ypbind: Host name lookup failure", and I have
to start it manually after boot :-(.
--
ni
That's what I get for reading code on a Sunday when kind of tired.
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Notice that immediately before the block you quite there is another
block:
#
# For now, we do not use the /etc/network/if-{up,down}.d
# stuff yet. Not sure if it is useful for NIS or how
# it should work, exactly.
#
return 0
which
Yes, I am positve that I have not modified the init script.
However, in the script I have, I find the following, which looks like it
would do what we are talking about.
#
# If the network is not up yet, do not start ypbind.
# We assume that /etc/network/ifup.d
Are you positive that you haven't modified the init script yourself?
While there is code in the init script that will try to do that it is
disabled since it is only partially implemented (as you have noticed).
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
ubuntu-b
What I am seeing with this is that the /etc/iniit.d/nis script will not
start if the network is not up, saying that it will be handled in if-
up.d
There is nothing to handle nis startup in if-up.d
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
ubuntu-bugs mailing
The problem could be resolved with "dpkg-reconfigure nis".
--
nis client seems to not start at boot
https://launchpad.net/bugs/50430
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
13 matches
Mail list logo
