Ubuntu
nis package

NIS not starting correctly which causes automount to fail to start

Bug #233807 reported by David
8
Affects Status Importance Assigned to Milestone
nis (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upgraded from Gutsy to Hardy. Rebooted my computer today after installing a bunch of upgrades through the Upgrade Manager.

Automounting started failing to mount my home directory. So I tried restarting autofs (automount) and saw that was failing because it couldn't get the mount points from NIS, where they are stored.

"ypcat -k auto.home" gave a message that it could not locate my NIS domain. So I restarted nis on the master server, then restarted nis on my computer, which is a secondary nis server, and ypcat started working again. This allowed autofs to start and everything works fine.

This is listed as Question #32163, and based on the responses is clearly a bug.

Thanks.

David

Revision history for this message
David (david-kahn) wrote :

I have since determined that it is not necessary to restart NIS in the master server, i.e, NIS only needs to be restarted on the slave server.

Revision history for this message
benmhall (ubuntu-linuxgruven) wrote :

I can confirm that this has been the case since at least Ubuntu 7.10.

In Q#32163, Art Cancro mentions resorting the start order to "fix" the problem. Indeed, the following solved my problem:

sudo mv /etc/rc2.d/S18nis /etc/rc2.d/S30nis

This is a serious bug for environments using Ubuntu with NIS and NFS. This was working properly in 6.06 and earlier and I can confirm that it breaks during upgrades. Since this fix seems so trivial, I hope that updated packages are released soon.

I work in a University setting where this would have been a big show stopper for deployment. I'm relieved that there is such a trivial workaround.

Revision history for this message
Andrew McCarthy (andrewmccarthy) wrote :

Confirming, as this seems to be a common issue (including me).

Revision history for this message
Michel M. (michel-mayrand) wrote :

We had the same problem here but after the /etc/rc2.d/S18nis to /etc/rc2.d/S30nis move we still had a few problems left with home automounting. Inspared by the solution, we move also /etc/rc2.d/S19autofs to /etc/rc2.d/S35autofs and it solved our home automounting last issues.

Revision history for this message
rohitunderhill (ro-rohitnet) wrote :

I am having the same problem, and delaying the startup does indeed seem to fix.
I do not have this problem on Ubuntu server (hardy) which does indeed use nis
and nis maps in the automounter. I think it is caused by the avahi system.

Revision history for this message
randallw (rwayth) wrote :

I tried disabling avahi-demon on my workstation and rebooting (with the default setup: S18nis and S19autofs in /etc/rc2.d/) and the problem still exists. So, it isn't avahi-demon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.