On 07/30/18 18:09, Rick Stevens wrote:
I expect this is a race condition with NetworkManager-
wait-online.service. By default, it does a oneshot of:
nm-online -s -q --timeout=30
and nm-online COULD return a 1 if NM is running but hasn't brought up
the network yet due to a slow DHCP response (if DHCP is being used). The
"-s" option returns 1 if NM has started whatever it has to on the
various NICs (e.g. spawned a dhclient) at boot, but it does NOT wait for
an actual network connection. Check journalctl for entries that read
something like:
NetworkManager-wait-online.service: Main process exited, code=exited,
status=1/FAILURE
The "status=1/FAILURE" indicates that NM was running, but the network
wasn't actually up yet so it couldn't do the mount. Using a fixed
IP/netmask/gateway on the client may get around this...or possibly not
using the "-s" on the nm-online command. Won't swear to it.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital
On 07/30/18 18:38, Ed Greshko wrote:
I'd never seen log entries like the type Bob posted.
FWIW, I did some googling and found several where the problem turned out to be
NetworkManager not running.
+
I dunno, but I have never had any [problem with NetWorkManager that I
recognized ...
At the moment I have feeding chores to do , be back later.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-27/64bit LINUX XFCE Fastmail POP3
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/CVGT67S7EGZYQ2JXDJC3WKCTPYEDYLDF/
