I suppose this is more of an FYI until I can determine where the bugzilla goes.....
If you use a "hostname" in your fstab for nfs mounts and your system is running bind and the resolv.conf is set to 127.0.0.1 the nfs mounts will fail at boot time. This is true even if you have NetworkManager-wait-online enabled and an entry for the host in the hosts file.
Examining the journal shows that the mount attempt happens prior to named getting started, obviously. :-)
Sort of leaning towards a systemd bugzilla
On 18/01/14 17:34, Ed Greshko wrote:
I suppose this is more of an FYI until I can determine where the bugzilla goes.....
If you use a "hostname" in your fstab for nfs mounts and your system is running bind and the resolv.conf is set to 127.0.0.1 the nfs mounts will fail at boot time. This is true even if you have NetworkManager-wait-online enabled and an entry for the host in the hosts file.
Examining the journal shows that the mount attempt happens prior to named getting started, obviously. :-)
Sort of leaning towards a systemd bugzilla
Does NetworkManager-wait-online actually still work in F19+? I have similar issues with autofs (ie IPA not available when autofs starts) and setting this in F18 and earlier solved the problem. Makes no difference in F19+.
On Sat, 18 Jan 2014 18:53:37 +0800 Ian Chapman packages@amiga-hardware.com wrote:
On 18/01/14 17:34, Ed Greshko wrote:
I suppose this is more of an FYI until I can determine where the bugzilla goes.....
If you use a "hostname" in your fstab for nfs mounts and your system is running bind and the resolv.conf is set to 127.0.0.1 the nfs mounts will fail at boot time. This is true even if you have NetworkManager-wait-online enabled and an entry for the host in the hosts file.
Examining the journal shows that the mount attempt happens prior to named getting started, obviously. :-)
Sort of leaning towards a systemd bugzilla
Does NetworkManager-wait-online actually still work in F19+? I have similar issues with autofs (ie IPA not available when autofs starts) and setting this in F18 and earlier solved the problem. Makes no difference in F19+.
Would having nm.service start earlier help?
Maybe a custom file? ------------------------------------- .include /usr/lib/systemd/system/NetworkManager.service [Unit] Before=nfs whatever # I don't use nfs currently,
save as /etc/systemd/system/NetworkManager.service
___ Regards, Frank www.frankly3d.com
On 18/01/14 20:03, Frank Murphy wrote:
Does NetworkManager-wait-online actually still work in F19+? I have similar issues with autofs (ie IPA not available when autofs starts) and setting this in F18 and earlier solved the problem. Makes no difference in F19+.
Would having nm.service start earlier help?
Actually I decided to have a another look and it's a bit more complicated than I first thought. Autofs is starting up after NetworkManager-wait-online but the problem was also that gdm doesn't. This means after boot up on this box, I can login before the network is fully ready which means I don't get a kerberos ticket and I'm unable to access NFS mounts etc. I suspect the reason why I never hit the gdm issue before was because I wasn't using a fast SSD, so the simple time it took to load X and GDM meant the network just happened to be ready by then. So the complete fix for me was to:
systemctl disable NetworkManager-wait-online systemctl disable autofs systemctl disable gdm
cp -a /usr/lib/systemd/system/{autofs.service,NetworkManager-wait-online.service,gdm.service} /etc/systemd/system/
Edit /etc/systemd/system/NetworkManager-wait-online.service and set: ExecStart=/usr/bin/nm-online -q --timeout=180
Edit /etc/systemd/system/autofs.service and set: After=network.target ypbind.service sssd.service NetworkManager-wait-online.service
Edit /etc/systemd/system/gdm.service and set: After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service NetworkManager-wait-online.service
systemctl daemon-reload systemctl enable NetworkManager-wait-online systemctl enable autofs systemctl enable gdm