On Mon, 2017-12-18 at 19:24 -0500, Sam Varshavchik wrote: > Gordon Messmer writes: > > > On 12/18/2017 05:52 AM, Sam Varshavchik wrote: > > > Time IP addresses > > > ======== ================== > > > 08:35:34 > > > 08:35:35 192.168.0.1 > > > > > > At 08:35:34 the server had no IP addresses > > > > > > Well, it probably had 127.0.0.1, which brings into question what the > > complete state of the network was. > > I'm pretty sure it does. My script only checks the IP addresses it knows > about. It doesn't check loopback. > > > Could you arrange to execute "ip addr show | logger" in your unfrak script? > > That way we get all of the interfaces and all of the addresses regardless of > > family. > > > > Could you also see if removing the "-s" flag from > > /usr/lib/systemd/system/NetworkManager-wait-online.service changes the > > behavior of the system? > > I'll do this at the first convenient opportunity. > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx I have now tried to do some sensible testing with the -s option in /usr/lib/systemd/system/NetworkManager-wait-online.service I have tested in groups of 10 reboots in the order shown A fail indicating that the NFS mount has failed with -s 2 fails in 10 no -s 0 fails in 10 with -s 3 fails in 10 no -s 0 fails in 10 no -s 0 fails in 10 with -s 4 fails in 10 I have not seen a single failure with the -s removed Hence my immediate problem appears to be solved! Many thanks _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
