[Bug 806284] Re: nfs-kernel-server fails: hostname "has non-inet addr" on boot, before eth0 comes up

2021-11-16 Thread Daniel Moyne
since installation of Ubuntu 20.04.3 LTS (Focal Fossa)20.04 nfs connection between client and server on my home lan is no more possible ; I removed autofs and firewall before using direct mount command on client with no success though the export check on server shows authorization ; everything has

[Bug 806284] Re: nfs-kernel-server fails: hostname has non-inet addr on boot, before eth0 comes up

2011-10-13 Thread Clint Byrum
This seems oddly similar to bug #862928 , which states that it is about NetworkManager, but is really the same problem. net-device-up IFACE!=lo is not sufficient. Some servers have many network interfaces, and the remote network services they provide should not be started until all of them are

[Bug 806284] Re: nfs-kernel-server fails: hostname has non-inet addr on boot, before eth0 comes up

2011-07-05 Thread Steve Langasek
On Wed, Jul 06, 2011 at 02:32:43AM -, 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