[Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
Same procedure as every year ... nis isn't working on 14.04 LTS, too! I agree, I looks like the main target is standalone computers or tablets, but not for computers in a productive environment. I will start starting CentOS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind 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/rpcbind/+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 believe the right place to export ON_BOOT=y is part of the /etc/init /portmap-wait.conf job. You should be able to confirm this locally by changing this line: start portmap || true to: start portmap ON_BOOT=y || true I'll prepare an upload to fix this. ** Package changed: nis (Ubuntu) => rpcbind (Ubuntu) ** Changed in: rpcbind (Ubuntu) Status: Incomplete => Triaged -- 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/rpcbind/+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
Ok, here's the problem: Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.910762] init: portmap main process (524) became new process (527) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921625] init: portmap state changed from spawned to post-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921947] init: portmap state changed from post-start to running Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.922172] init: Handling started event Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.922498] init: ypbind goal changed 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. Going back a bit in the boot: Jun 5 22:24:03 intwinxpubuntu6 kernel: [5.844424] init: Handling remote-filesystems event Jun 5 22:24:03 intwinxpubuntu6 kernel: [6.950731] init: Handling local-filesystems event Jun 5 22:24:03 intwinxpubuntu6 kernel: [7.038074] init: Handling filesystem event Jun 5 22:24:04 intwinxpubuntu6 kernel: [7.415998] init: statd-mounting goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [7.422316] init: statd-mounting state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.364354] init: statd goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.371049] init: statd state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.377212] init: statd state changed from starting to pre-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.405912] init: statd pre-start process (489) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.565510] init: portmap-wait (statd) goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.565696] init: portmap-wait (statd) state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.566173] init: portmap-wait (statd) state changed from starting to pre-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.566342] init: portmap-wait (statd) state changed from pre-start to spawned Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.600918] init: portmap-wait (statd) main process (505) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.601291] init: portmap-wait (statd) state changed from spawned to post-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.611092] init: portmap-wait (statd) state changed from post-start to running Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.816319] init: portmap goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.816509] init: portmap state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.816991] init: portmap state changed from starting to pre-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.844586] init: portmap pre-start process (522) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.848499] init: portmap pre-start process (522) exited normally Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.848698] init: portmap state changed from pre-start to spawned Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.876393] init: portmap main process (524) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.882281] init: portmap main process (524) executable changed Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.910762] init: portmap main process (524) became new process (527) Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921625] init: portmap state changed from spawned to post-start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921947] init: portmap state changed from post-start to running Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.922498] init: ypbind goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.922676] init: ypbind state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.923185] init: ypserv goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.923359] init: ypserv state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.923996] init: gssd goal changed from stop to start Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.928775] init: gssd state changed from waiting to starting Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.939997] init: portmap-wait (statd) goal changed from start to stop Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.943619] init: portmap-wait (statd) state changed from running to pre-stop Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.950994] init: portmap-wait (statd) state changed from pre-stop to s
[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
Re: [Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
On Tue, Jun 05, 2012 at 12:33:14PM -, alex wrote: > If I try to start ypbind: > # start ypbind > start: Job is already running: ypbind When this happens, it may be useful to grab the output of 'status ypbind' as well. But regardless, your log shows the same hostname lookup failure, so we'll need to see the syslog output when booting with --verbose to understand why. -- 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
Re: [Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
On Tue, Jun 05, 2012 at 02:25:02PM -, vagk wrote: > I changed the interfaces file to get static ip and retried. This should not matter because dhclient doesn't return control to ifupdown until it successfully acquires an IP. > 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 That's because you had invalid network configuration information: you were no longer using DHCP, but had not specified another source for DNS server information. > So I removed package resolvconf (which I don't like in lab setups, same > as network-manager) and voila! resolvconf is the supported mechanism for managing /etc/resolv.conf in 12.04. Outside of your experiments here for debugging, I strongly advise that you keep it installed. > I rebooted and now I there was a 10 second delay before lightdm started > and ypbind got running. What is the system doing during this 10 second delay? > 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 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. -- 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
>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
Just FYI, I'm playing now with a fresh new vitual (VBOX) Ubuntu12.04 64bit (don't want to damage a more or less running system) and got the same behaviour with a non working nis environment. The only packages I added via apt- get are nis, autofs, tcsh, csh, nfs-kernel-server: After a local login I did: # ypwhich ypwhich: Can't communicate with ypbind I also cannot find any process (i.e. ps -ef | grep yp) which seems to be related with ypbind! If I try to start ypbind: # start ypbind start: Job is already running: ypbind But I could not see it (again looking at the snapshot of the current processes with root privilegies)!! If i restart ypbind (# restart ypbind) process is obviously restarting and nis is running. >From my humble point of view this bug must pain a lot of Ubuntu user all over >the world. Alex -- 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 compared ypbind.log with a proper working machine, and I could not find any differences. /etc/yp.conf exists and nis servers responding ping packages as expected. ** Attachment added: "ypbind.conf debug" https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3175933/+files/ypbind.conf -- 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
Re: [Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
On Mon, Jun 04, 2012 at 02:43:32PM -, 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
[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 2>&1 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
[Bug 1007293] Re: nis doesn't work anymore after upgrade to 12.04
Oh sorry, I forgot the content of /etc/default/nis Alex ** Attachment added: "conttent of /etc/default/nis" https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3174700/+files/nis -- 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
Hi Steve, hi Clint, thanks for answer and sorry for delay: # initctl list | grep yp ypbind start/running, process 1256 ypserv stop/waiting ypxfrd stop/waiting start-ypbind stop/waiting yppasswdd stop/waiting Best regards Alex ** Attachment added: "content of /etc/init" https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1007293/+attachment/3174674/+files/init.tar.gz -- 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
hi alex, It would also be helpful to see the output of this command as root: initctl list | grep yp and to have the contents of /etc/default/nis attached. -- 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
alex, this is somewhat surprising to hear, as up until 12.04, NIS was actually quite broken on bootup for most users due to many race conditions in the way it started up. In 12.04, the startup was moved to being managed by upstart jobs, and this fixed the problem for many users (in fact we have updates pending for 10.04 to fix this for those users). Could you perhaps create a tarball of /etc/init from a machine that is affected, and attach it to this bug report? Try: tar -cz -f init.tar.gz -C /etc init Thanks! Also if you can run this command on an affected machine, it will help us verify the versions of software you have: apport-collect 1007293 (Marking as High Importance, Incomplete). ** Changed in: nis (Ubuntu) Status: New => Incomplete ** Changed in: nis (Ubuntu) Importance: Undecided => High -- 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
OK, I'm speaking now only of a new installed UBUNTU 12.04LTS system: NIS is not working after reboot, on my other machines (Ubuntu 10.04-11.10 and Debian 6) it works very well. Your hint does not have any positiv effects and I don't understand the logic behind. Why should I remove configuration files in my home directory if I'm not able to login. I have to restart nis manually, than it works. Maybe this bug has more side effects, because: automounts are not working too! After some hours tear at one's hair: removing network-manager and editing /etc/network/interfaces: no success, network response is very slow (i.e. ping). reinstalling netork-manager and reconfigure new, commenting out everithing in /etc/network/interfaces: network response is OK again, nis is working after reboot!!! What's going on? But autofs is still not running: I give up for today and create static mounts. No hints, no messages, just not working. -- 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 will help you, do the following. go to console (alt+ctrl+f1/f2.f6) and apply the command rm -rf .gnome .gnome2 .gconf .gconfd .metacity after this restart your system. try this command -- 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
