[Bug 993259] Re: ypbind does not start on boot
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 skips if it can't resolve the server name, but keeps on running when it probably can't connect the server yet? And no i don't want to have static IPs in all clients as i quite trust my DHCP servers and i always prefer FQDN for network migrations. -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 experienced is that doesn't make a difference i we change for YPBINDARGS=-no-dbus to YPBINDARGS= in /etc/default/nis, as this is ypbind's connection to NM. -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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. 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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: after booting ypwhich says ypwhich: Can't communicate with ypbind, and it works after I restart ypbind. -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 management of the dependency of nis on a working network interface is not correctly done ** Changed in: nis (Ubuntu) Status: Invalid = Confirmed -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 address it will start and bind when the network is up. -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 = Invalid -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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: [ifupdown] managed=false -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 .backgrounded During boot it thinks there is no nis server in yp.conf. If i put a sleep statement at the bottom of the /etc/init/ypbind.conf pre-start script section, its seems to work. I have to crank the sleep to 10 seconds to get it to work. -- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
-- 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/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
