On Wed, Jul 06, 2011 at 02:32:43AM -0000, John Gilmore wrote:
> The problem appears to occur because NetworkManager is still in the
> process of bringing up the network interface (according to other
> interleaved syslog reports). These hostnames need DNS from another
> server to resolve them.
> The root cause of the problem appears to be that Natty doesn't make the
> nfs-kernel-server service wait until the first Ethernet comes up. Thus,
> nfs-kernel-service can't resolve domain names in the /etc/exports file,
> and it produces this very confusing message and doesn't actually export
> the filesystems.
That's correct. The /etc/init/rc-sysinit.conf job waits for the loopback
interface to be up, but does not wait for other interfaces; this is
consistent with the historical guarantee provided by pre-upstart init
scripts on Ubuntu as well, but as boot becomes faster it's more common to
lose a race against the network.
Ultimately, nfs-kernel-server should switch to using a native upstart job,
and should probably be set to start on net-device-up IFACE!=lo by default.
** Changed in: nfs-utils (Ubuntu)
Status: New => Triaged
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806284
Title:
nfs-kernel-server fails: hostname "has non-inet addr" on boot, before
eth0 comes up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/806284/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
