I also discovered the problem with 12.04 where exportfs fails at boot.
In the log /var/log/boot.log I had errors for each client name
e.g. exportfs: Failed to resolve clientname
Search I found there are a number of trivial workarounds.
- Adding the names to /etc/hosts.
- Using IP numbers in
Clint: Any progress on this?
Would the following work:
- Introduce new network-has-address event.
- Change our scripts to emit this event at the same time as network-static-up
when we have a non-loopback interface configured.
- Add a Network Manager hook to emit it too.
- Implement a
This is affecting me as well. It started when I upgraded from 11.04 to
11.10.
I am identifying machines with IPs, not DNS. I set it up as per this
tutorial:
https://mostlylinux.wordpress.com/network/nfshowto/
These instructions work fine for 10.04, 10.10, and 11.04. (However, the
commands it
I can confirm this issue. It seemed to have either started after
upgrading to 11.10 from 11.04, or after changing my exports from IPs to
DNS names. Apparently, it was both.
I did see an error message the other day which said that NFS was unable
to resolve DNS, but I couldn't remember where it
Joseph, this doesn't sound related. The issue here is that if you
configure nfs exports that need DNS, you either need to configure a
static network interface in /etc/network/interfaces instead of network-
manager, or you need to refresh exports every time network interfaces
come up.
--
You
I've run into a similar issue after upgrading from 11.04 to 11.10 on
server:
$ showmount server
Hosts on server:
192.168.111.110
192.168.111.57
By placing the following in the fstab of clients, resolved consistent
nfs halts:
server:/path /local/path nfs proto=udp
The halts were occurring
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.
Ok, reversing my position after talking with Clint on IRC. :)
We can't delay the static-network-up event because doing so would slow
down the entire desktop boot sequence for all users. This needs to be
fixed instead by converting nfs-kernel-server to use an upstart job
that's 'start on [...]
** Changed in: nfs-utils (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848823
Title:
nfs-kernel-server requires a real interface to be up
To manage
Reassigning to ifupdown after talking to Steve again. Reducing
importance to Medium since there is a workaround and no new regression.
** Package changed: nfs-utils (Ubuntu) = ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Importance: High = Medium
** Changed in: ifupdown (Ubuntu)
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
11 matches
Mail list logo
