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

[Steve Atwell]

I don't see the point of checking whether NEED_IDMAPD=yes is in
/etc/default/nfs-common.  The "script" block is only going to run when
the pre-script determines that idmapd should be started.  (Even if you
did need to check NEED_IDMAPD, you'd want to read it out of the
environment rather than grepping the defaults file.)

It looks like your proposed solution boils down to copying what the
rpc_pipefs upstart job does into the idmapd job.  This seems like a
possible workaround, but definitely not a fix.

-- 
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