On 19 Dec 2017 07:49, <Francis.Montagnac(a)inria.fr> wrote:
On Mon, 18 Dec 2017 14:12:55 -0800 Gordon Messmer wrote:
On 12/17/2017 01:17 PM, Francis.Montagnac(a)inria.fr wrote:
> Dec 17 21:32:59 X systemd: Mounting /data2...
> Dec 17 21:33:19 X mount: mount to NFS server 'Y' failed:
Resource temporarily unavailable, retrying
> Dec 17 21:33:19 X systemd: Mounted /data2.
Can you reproduce that condition and then get the output of
status NetworkManager-wait-online"? That should confirm that the
ExecStart process does not include the -s flag.
Here it is:
systemctl status NetworkManager-wait-online
. NetworkManager-wait-online.service - Network Manager Wait Online
disabled; vendor preset: enabled)
Active: active (exited) since Tue 2017-12-19 07:58:05 CET; 4min 12s
Process: 743 ExecStart=/usr/bin/nm-online -q --timeout=30
Main PID: 743 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Dec 19 07:57:58 X systemd: Starting Network Manager Wait Online...
Dec 19 07:58:05 X systemd: Started Network Manager Wait Online.
journalctl -b -u data2.mount
-- Logs begin at Thu 2015-04-09 18:41:55 CEST, end at Tue 2017-12-19
08:01:55 CET. --
Dec 19 07:58:05 X systemd: Mounting /data2...
Dec 19 07:58:25 X mount: mount to NFS server 'Y' failed: Resource
temporarily unavailable, retrying
Dec 19 07:58:25 X systemd: Mounted /data2.
The setup of this server is:
eth0 static IP declaration with dns servers and gateway
eth0.2006 static IP declaration: additionnal vlan interface
with the associated port on a cisco switch configured as:
switchport trunk native vlan 390
switchport trunk allowed vlan 390,2006
switchport mode trunk
storm-control broadcast level 5.00 3.00
no cdp enable
/etc/resolv.conf was generated by NetworkManager at the same second
indicated by nm-online:
Size: 76 Blocks: 8 IO Block: 4096 regular file
Device: 806h/2054d Inode: 19924685 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-12-19 07:58:05.539740447 +0100
Modify: 2017-12-19 07:58:05.437735660 +0100
Change: 2017-12-19 07:58:05.438735707 +0100
The 'Y' server is in the eth0 subnet.
'Y' has to be resolved by the DNS.
As said before, even pinging the gateway IP succeeds only more than
20s after the routes (as seen by "ip route") are defined.
Cisco switch and that delay for traffic on a static address?
Sounds like symptoms of STP delaying s port from listening to forwarding...
Have you looked at disabling on that interface or setting portfast if it's
only host facing?