[Bug 848823] Re: nfs-kernel-server requires a real interface to be up

[Clint Byrum]

Excerpts from Steve Langasek's message of Tue Sep 20 20:09:58 UTC 2011:
> No, nfs-kernel-server isn't failing to *start*; the "access denied" from
> the bug description contradicts this.  All signs point to this being a
> race caused by nfs-kernel-server starting before DNS is available
> (because the network isn't up yet), causing hostnames in the config to
> fail to resolve.
> 
> It's true that ifupdown hasn't regressed vs. how we were starting
> runlevel 2 before, but it's still buggy, because classically init
> scripts in runlevel 2 are allowed to assume that the network is fully up
> before they're called.  When we changed this to only wait for lo, it was
> a compromise because we hadn't worked out a way to keep the boot from
> hanging forever in the case of problems.  Now that we have a way to do
> that, we should use it, deferring the static-network-up event until at
> least one non-loopback interface is up even when all interfaces are
> managed by NM.  No additional delay if the network config actually *is*
> static, and more robust handling of init scripts if it isn't.
> 
> (Clint, I've assigned this bug back to you as part of the reassignment
> to ifupdown, but if this isn't on your priority list, feel free to
> unassign... or assign it to one of your colleagues :)

That all makes sense Steve, and I hadn't thought about DNS problems.

The current situation where static-network-up is emitted only when
/etc/network/interfaces is handled is a compromise to keep from regressing
the desktop boot speed waiting for connections that may never come.

We could probably interrogate NetworkManager and find out if there are
"boot time" network interfaces that are going to be brought up, and if so,
delay while waiting for those. I'll keep this task as part of ifupdown
and see if we can do just that early in the next dev cycle.

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

Title:
  nfs-kernel-server requires a real interface to be up

Status in “ifupdown” package in Ubuntu:
  Triaged

Bug description:
  For the last few weeks whenever I try to mount a nfs share from
  another machine, I get an access denied message from the server.

  once I restart via 'service nfs-kernel-server restart', then it starts
  working again. This is required atleast once per day.

  nfs server is running on fully updated 11.10 onieric
  clients are on 11.04 and 10.04

  I never experienced such issues prior to 11.10

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nfs-kernel-server 1:1.2.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Tue Sep 13 20:02:19 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nfs-utils
  UpgradeStatus: Upgraded to oneiric on 2011-08-13 (31 days ago)

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