Comment 1 for bug 806284
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 806284] [NEW] nfs-kernel-server fails: hostname "has non-inet addr" on boot, before eth0 comes up | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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/
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.