On Mon, Jun 04, 2012 at 02:43:32PM -0000, vagk wrote: > I inserted > exec > /var/log/nis-debug.log 2>&1 > in /etc/init/ypbind.conf after script line
That really shouldn't be necessary. You should be able to read the log files from /var/log/upstart, without modifying the upstart job. alex, do you have any interesting log files in /var/log/upstart on your system related to ypbind? > 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 There's no reason for this that I can see, if your network is configured in /etc/network/interfaces. The ypbind job itself is configured to start only after the network is up. ypbind may also be started by the start-ypbind job, but this job also only starts in response to a series of other jobs that all wait for the network. 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? > 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.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 This is quite unusual since as I said, each of these other services (atd and lightdm) are supposed to wait for events ('runlevel 2') that are themselves dependent on the network being up. You may also want to boot with --verbose on the kernel commandline, so that we can see exactly what order the upstart events are firing in. -- 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