[Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
alex, vagk: could each of you please set YPBINDARGS=-no-dbus -debug in /etc/default/nis, reboot, and attach /var/log/upstart/ypbind.log so we can see exactly what's failing? Here is an excerpt of the /var/log/upstart/ypbind.log when it fails to start Setting NIS domainname to: sch.local 571: parsing config file 571: Trying entry: ypserver nisserver 571: parsed ypserver nisserver 571: add_server() domain: sch.local, host: nisserver, slot: 0 571: Host name lookup failure 571: No entry found. 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 Although my understanding of upstart procedures is minimal this line in /etc/init/ypbind.conf got me curious and ((filesystem and static-network-up) or failsafe- boot))) My setup in /etc/network/interfaces (as stated in my previous post) is to get ip from dhcp ( which by the way I assign based on mac to be always the same) I changed the interfaces file to get static ip and retried. It failed but for a different reason. My /etc/yp.conf has no direct ip but a cname ypserver nisserver When networking got up /etc/resolv.conf was empty and that is because resolvconf package deleted the information that the last dhclient command wrote to /etc/resolv.conf So I removed package resolvconf (which I don't like in lab setups, same as network-manager) and voila! I rebooted and now I there was a 10 second delay before lightdm started and ypbind got running. So to conclude : Static IP on /etc/network/interfaces and nis server by IP in /etc/yp.conf works (or by cname and without resolvconf package) IP from dhcp on /etc/network/interfaces does not work. It seems that ypbind starts before networking Changing to static ips on 30+ clients is not an option for a lot of reasons. By the way my tests are also in a vbox that was running 10.04 with no problems (with just nis and nfs client packages added) and was upgraded to 12.04. -- 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/1007293 Title: nis doesn't work anymore after upgrade to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+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 1007293] Re: nis doesn't work anymore after upgrade to 12.04
I'm still lacking the debugging information to see why it's starting before networking for you. For that I need to see the syslog output of a boot with --verbose. changed grub parameters to nosplash debug --verbose and I am attaching the syslog file Do you want also the syslog if the static ip situation that worked? ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3176658/+files/syslog -- 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/1007293 Title: nis doesn't work anymore after upgrade to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+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 1007293] Re: nis doesn't work anymore after upgrade to 12.04
This shows that ypbind is being started as soon as portmap starts. But the start condition for ypbind is: start on (started portmap ON_BOOT= or (started portmap ON_BOOT=y and ((filesystem and static-network-up) or failsafe-boot))) So it appears that portmap is being started with ON_BOOT= instead of with ON_BOOT=y, confusing ypbind into believing that as soon as portmap starts, ypbind can also be started. I believe this is due to a bug in either the portmap-wait or the statd job, one of which needs to set ON_BOOT=y. I tried changing /etc/init/ypbind.conf reversing the conditions just to test start on (started portmap ON_BOOT=y or (started portmap ON_BOOT= and ((filesystem and static-network-up) or failsafe-boot))) The boot process delayed in 2 points (between 9 to 19 sec and after 30 sec) ypbind started successfully! Does this verify your assumptions of where the problem is? -- 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/1007293 Title: nis doesn't work anymore after upgrade to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+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 1007293] Re: nis doesn't work anymore after upgrade to 12.04
I am having similar issues concerning nis after upgrading to ubuntu 12.04 ypbind does not start on boot. The status command does not show a running process service ypbind status ypbind start/running nor ps -A | grep ypbind I inserted exec /var/log/nis-debug.log 21 in /etc/init/ypbind.conf after script line and the output in nis-debug.log was 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. my /etc/yp.conf is ypserver nisserver (nisserver is resolved by dns ok, tried to use the ip but the problems seems elsewhere) I dont use network-manager (purged) and my /etc/network/interfaces file is the following allow-hotplug lo eth0 auto lo eth0 iface lo inet loopback iface eth0 inet dhcp The problem seems to be that when ypbind is initially started networking is not up yet For now I execute manually after each boot the following command (I will probably add it at /etc/rc.local although this is ugly) service ypbind restart Some lines from /var/log/syslog showing that ypbind is started before networking and although it is respawning it does not succeed Jun 4 16:47:48 ubuntutestclient ypbind: Host name lookup failure .. Jun 4 16:47:48 ubuntutestclient dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Jun 4 16:47:48 ubuntutestclient dhclient: DHCPREQUEST of 192.168.10.53 on eth0 to 255.255.255.255 port 67 Jun 4 16:47:48 ubuntutestclient dhclient: DHCPOFFER of 192.168.10.53 from 192.168.10.165 Jun 4 16:47:48 ubuntutestclient dhclient: DHCPACK of 192.168.10.53 from 192.168.10.165 Jun 4 16:47:48 ubuntutestclient rpcbind: Cannot open '/run/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory) Jun 4 16:47:48 ubuntutestclient rpcbind: Cannot open '/run/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory) Jun 4 16:47:48 ubuntutestclient kernel: [8.984711] init: portmap-wait (statd) main process (531) killed by TERM signal .. Jun 4 16:47:48 ubuntutestclient kernel: [9.448250] init: ypbind main process (583) terminated with status 1 Jun 4 16:47:48 ubuntutestclient kernel: [9.448372] init: ypbind main process ended, respawning .. Jun 4 16:47:54 ubuntutestclient kernel: [ 15.403354] init: wait-for-state (atdypbind) main process (1071) killed by TERM signal Jun 4 16:47:54 ubuntutestclient kernel: [ 15.423670] init: wait-for-state (gdmypbind) main process (1076) killed by TERM signal Jun 4 16:47:54 ubuntutestclient kernel: [ 15.429334] init: wait-for-state (lightdmypbind) main process (1084) killed by TERM signal I have 30 client machines with about 300 users in a school and this is a serious issue that prevents me from upgrading yet. Please look into it and I will try to help as much as I can -- 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/1007293 Title: nis doesn't work anymore after upgrade to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+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
