[Bug 643289] Re: idmapd does not starts to work after system reboot

[Leonardo Borda]

Hi Guys,

I reproduced the issue using Steve Atwell's modification in
/etc/init/rpc_pipefs.conf and I am able to reproduce the same issue in a
stock Lucid install.

It looks like /etc/init/idmapd.conf needs also another if statement that
checks whether the client is using nfsv4 or not. I made a small change
to the upstart script and now I don't see the issue anymore. Idmapd
start successfully and I am able to mount using krb5.

Here is what I did:
I've changed the last statement (script/end script) in /etc/init/idmapd.conf to the following:

script
	if [ -f "$DEFAULTFILE" ]; then
		. "$DEFAULTFILE"
		#
	        # We also need to check in /etc/default/nfs-common if the client wants to use nfs4
	        #
	        if  grep -q "NEED_IDMAPD=yes" $DEFAULTFILE ; then
	                mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs
	        fi

	fi
		exec rpc.idmapd
end script

Can you guys check on your side as well?

Leonardo

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/643289

Title:
  idmapd does not starts to work after system reboot

Status in “mountall” package in Ubuntu:
  Triaged
Status in “nfs-utils” package in Ubuntu:
  Triaged
Status in “mountall” source package in Lucid:
  Triaged
Status in “nfs-utils” source package in Lucid:
  Triaged

Bug description:
  Binary package hint: nfs-common

  I have server which runs Kerberos+LDAP+NFSv4. After installing minimal Ununtu 10.10, I set up Kerberos client and NFSv4. But I've got a problem when restarted computer. After some retries I've noticed that idmapd does not work properly after system restarts but there is a workaround which makes it work:
  1. Edit /etc/rc.local and place there following commands
  sleep 5
  service autofs stop
  service idmapd restart
  service autofs start
  2. Add rc.local to system startup:
  update-rc.d rc.local enable

  Hope this workaround will help to find out the source of the problem.
  It is obvious that something launches in wrong way. But what is that?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/643289/+subscriptions