On 07/31/18 06:09, Rick Stevens wrote:
On 07/30/2018 02:56 PM, Bob Goodwin wrote:
> On 07/30/18 17:46, Ed Greshko wrote:
>> If you do
>>
>> journalctl -b 0 | grep mount
>>
>> on the client, what does it show?
> +
>
> I guess this is not to long to send the entire result -
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.
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.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.