[Bug 933575] Re: NFS not being mounted at boot time - rpc.statd is not running but is required for remote locking

[Steve Langasek]

On Fri, Feb 17, 2012 at 09:09:13AM -0000, mastro wrote:
> This is to say that I can't test on that server anymore.  If you can wait
> I'll be able to do tests after 22/02/2012 when this server will be taken
> off-line.

Ok, that would be fine.

> but I doubt that second try is performed by the bootup.. it's more like
> it's the log from my cron script trying.

You can take my word for it.  That's how mountall works, and no output from
your cron jobs ever lands in the boot.log.

> I don't know the bootup process in details and what does print that
> message, but the common meaning of "Name or service not known" is DNS
> failure, which doesn't make sense on an IP address.

It's arguably a bug that mount.nfs tries to pass an IP address to the
resolver, but that's not the bug that's causing your problem.

> do you know of anyway of making the networks logs be more verbose without
> upgrading the server?  I'm fine modifying the bootup scripts if you give
> me precise instructions

If you don't have a spare machine you can run a test from, and you aren't
prepared to upgrade this server to a pre-release version of 12.04 (which is
completely understandable), the next best thing would be to install the
upstart package from precise directly; there's no really good way to get
better logging just by modifying the boot scripts.  However, installing the
upstart package will also require versions of the ifupdown and initscripts
packages from Ubuntu 11.10 or later.

Is there any reason this server is at 11.04 still?  If it could be upgraded
to 11.10 and the precise upstart package installed from there, that might be
the best option.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org

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

Title:
  NFS not being mounted at boot time - rpc.statd is not running but is
  required for remote locking

Status in “nfs-utils” package in Ubuntu:
  Incomplete

Bug description:
  Version: Ubuntu SERVER 11.04

  installed nfs-commons

  added this to /etc/fstab:

  192.168.88.252:/repo  /mnt/repos   nfs     rw,hard,intr  0     0

  but I also tried
  192.168.88.252:/repo  /mnt/repos   nfs      _netdev,rw,hard,intr
  192.168.88.252:/repo  /mnt/repos   nfs      defaults,_netdev,rw,hard,intr

  
  with
  mnt /mnt/repos

  it works.

  reboot.

  I don't get the NFS up at boot time.

  I access to the server with SSH, eth0 and network is fine
  no NetworkManager
  no gui

  mount -a

  it works...

  so to debug the issue I added this to /etc/rc.local (before exit 0)

   mount /mnt/repos > /tmp/mounting.$$ 2>&1

  rebooted and I got this in that file:

  
  mount.nfs: rpc.statd is not running but is required for remote locking.
  mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
  mount.nfs: an incorrect mount option was specified


  I can't get NFS being mounted at boot time.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Package: mountall 2.25ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-13.55-server 2.6.38.8
  Tags:  natty
  Uname: Linux 2.6.38-13-server x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/933575/+subscriptions