After some more testing, it's definitely a DNS issue on probably early
boot stages without network. So there are two ways to workaround:
1. Only use IP addresses in /etc/yp.conf
2. Add your NIS server to /etc/hosts
I am using the later one on Ubuntu 14.04.
But i still don't why ypbind will skip
It's still an issue in the upcoming LTS release. We really need to fix
it, as there are still a lot of company where they run a secured NIS
installations.
As it's somehow an DNS issue, there should be something like a respawn
from upstart everytime there is a network change. What i also
experience
I worked around this by putting the server name and IP address into
/etc/hosts.
My network initialization is static.
managed=false was already set.
Looks like a DNS issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu
I am, for some reason, now getting ypbind and autofs working on boot up
by adding restarts for both services to /etc/rc.local. Sometimes I have
to wait a while before logging in for it to work. No idea what has
changed.
--
You received this bug notification because you are a member of Ubuntu
Se
I do not believe this is a NetworkManager issue.
My interfaces file says:
auto eth0
iface eth0 inet dhcp
and my /etc/NetworkManager/NetworkManager.conf says:
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
However I still have this exact same issue as reported above: aft
it is an error for ypbind to not start correctly when the network
interface is managed by network-manager and thus comes up a bit slowly
of course, changing the configuration to not rely on network-manager, as
explained in comment #3 is a workaround
still i would consider this a bug: the manageme
This may help if you have this issue with ypbind trying to start and the
network not up yet:
Use IP addreses in /etc/yp.conf
for example:
domain your_nis_domain server 10.10.123.123
If the network is not up, ypbind starts and cannot reslove the hostname in
yp.conf and dies.
If you supply an IP
John,
Based on your good information in the comments, I'm marking this as invalid.
If you think that there is something that could be done to fix this
situation, please explain and set the bug to 'New'.
Thank you for your time.
Scott
** Changed in: nis (Ubuntu)
Status: New => Inval
The problem is with NetworkManager. If the system boots with ifup and DHCP
ypbind starts fine.
That is uncomment the iface etho line in /etc/network/interfaces and make sure
the following entry is in /etc/NetworkManager/NetworkManager.conf so that
NetworkManager does not control the interface:
So the network is taking a really long time to come up using DHCP. I found that
the
entry in /etc/network/interfaces had the iface eth0 inet dhcp entry commented
out
as shown below. If I un-comment the "iface etho inet dhcp" entry things work,
the
network comes up fast and ypbind starts. It appe
I confirmed this bug on 4 systems. Here is the output from
/var/log/upstart/ypbind.log:
Setting NIS domainname to: sunrize
No NIS server and no -broadcast option specified.
Add a NIS server to the /etc/yp.conf configuration file,
or start ypbind with the -broadcast option.
Binding to YP server ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/993259
Title:
ypbind does not start on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+b
12 matches
Mail list logo
