Bug#860264: Acknowledgement (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

2018-11-27 Thread Gabriel Filion
On Sat, 1 Sep 2018 03:16:34 -0400 Gabriel Filion wrote: > > wooledg:~$ cat /lib/systemd/system/networking.service > > [...] > > [Service] > > Type=oneshot > > EnvironmentFile=-/etc/default/networking > > ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n > > "$(ifquery

Bug#860264: Acknowledgement (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

2018-09-01 Thread Gabriel Filion
Hi! I'm currently experiencing the exact same issue with an NFS mount for /home, and another nfs mount (from another server) that gets mounted under /srv/something: at boot, nfs mount times out, and afterwards when the boot is complete, if I ssh in and execute "mount -a" as root the mount points

Bug#860264: Acknowledgement (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

2017-04-17 Thread Greg Wooledge
I believe I was able to get this working by making a change to the /etc/network/interfaces file: # allow-hotplug eth0 auto eth0 iface eth0 inet dhcp I replaced the allow-hotplug with auto. Now, after booting, it appears to be working: wooledg:~$ sudo systemctl status nfs-server *