2

I am setting up a server which has a 4 ports (em1 to em4) QLogic network interface. It is connected though em3 and the IP address is automatically given by DHCP based on the mac address. I do not have access to the network after booting.So, I have to use systemctl restart network after each boot.

After booting, systemctl status network sometimes gives me this :

network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since ven. 2019-03-15 09:20:18 CET; 2min 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1365 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

mars 15 09:19:32 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
mars 15 09:19:32 localhost.localdomain network[1365]: Activation de l'interface loopback :  [  OK  ]
mars 15 09:20:18 localhost.localdomain network[1365]: Activation de l'interface em3 :  Erreur : l'activation de la connexion a échoué : La configuration IP n'a pas pu être réservée (aucun adresse disponible, délai d'expiration, etc. )
mars 15 09:20:18 localhost.localdomain network[1365]: [ÉCHOUÉ]
mars 15 09:20:18 localhost.localdomain systemd[1]: network.service: control process exited, code=exited status=1
mars 15 09:20:18 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
mars 15 09:20:18 localhost.localdomain systemd[1]: Unit network.service entered failed state.
mars 15 09:20:18 localhost.localdomain systemd[1]: network.service failed.

Clearly, the network is not activated. But sometimes (apparently randomly), I can also have after a boot:

network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: active (exited) since ven. 2019-03-08 15:05:10 CET; 48s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2781 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
  Process: 3019 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)

mars 08 15:05:09 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
mars 08 15:05:09 localhost.localdomain network[3019]: Activation de l'interface loopback :  [  OK  ]
mars 08 15:05:09 localhost.localdomain network[3019]: Activation de l'interface em3 :  Connexion activée (chemin D-Bus actif : /org/freedesktop/NetworkManager/ActiveConnection/5)
mars 08 15:05:09 localhost.localdomain network[3019]: [  OK  ]
mars 08 15:05:10 localhost.localdomain systemd[1]: Started LSB: Bring up/down networking.

but although the connection seems activated I have to restart to access the network.

Let me add that /etc/sysconfig/network-scripts/ifcfg-em3 contains :

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=em3
UUID=442f***************************
ONBOOT=yes
IPV6_PRIVACY=no

As ONBOOT is set to yes, I do not know how to fix this issue.

PS : when looking in /var/log/message (only the lines including networkManager), I have on booting time :

 Mar 15 09:10:59 localhost NetworkManager[1148]: <info>  [1552637459.9299] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-em3 (442f*****************,"em3")
Mar 15 09:11:01 localhost NetworkManager[1148]: <info>  [1552637461.9915] manager: (em3): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Mar 15 09:11:01 localhost NetworkManager[1148]: <info>  [1552637461.9924] device (em3): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 15 09:11:01 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): em3: link is not ready
Mar 15 09:11:02 localhost kernel: bnx2x 0000:01:00.2 em3: using MSI-X  IRQs: sp 85  fp[0] 87 ... fp[7] 94
Mar 15 09:11:02 localhost kernel: bnx2x 0000:01:00.2 em3: NIC Link is Up, 1000 Mbps full duplex, Flow control: none
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.2490] device (em3): link connected
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5636] device (em3): state change: unavailable -> disconnected (reason 'none') [20 30 0]
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5657] policy: auto-activating connection 'em3'
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5668] policy: auto-activating connection 'em3'
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5682] device (em3): Activation: starting connection 'em3' (442f********************)
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5683] device (em3): disconnecting connection 'em3' for new activation request
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5683] device (em3): state change: disconnected -> deactivating (reason 'new-activation') [30 110 60]
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5691] device (em4): Activation: starting connection 'em3' (442f************************)
Mar 15 09:11:02 localhost NetworkManager[1148]: <info>  [1552637462.5702] device (em3): state change: deactivating -> disconnected (reason 'new-activation') [110 30 60]
Mar 15 09:11:02 localhost nm-dispatcher: req:2 'down' [em3]: new request (4 scripts)
Mar 15 09:11:02 localhost nm-dispatcher: req:2 'down' [em3]: start running ordered scripts...
Mar 15 09:11:30 localhost NetworkManager[1148]: <info>  [1552637490.3692] device (em4): disconnecting connection 'em3' for new activation request
Mar 15 09:11:30 localhost NetworkManager[1148]: <info>  [1552637490.3704] audit: op="connection-activate" uuid="442f*********************" name="em3" pid=1484 uid=0 result="success"
Mar 15 09:11:30 localhost NetworkManager[1148]: <info>  [1552637490.3909] device (em4): Activation: starting connection 'em3' (442f*******************)
Mar 15 09:11:55 localhost network: Activation de l'interface em3 :  Connexion activée (chemin D-Bus actif : /org/freedesktop/NetworkManager/ActiveConnection/3)

First, there seems to have interactions between em3 and em4 and at no point I have thing such as the following that happened when systemctl restart network :

localhost NetworkManager[14060]: <info>  [1552637774.4521] device (em3): Activation: starting connection 'em3' (442f**********************)
localhost nm-dispatcher: req:2 'down' [em3]: new request (4 scripts)
localhost nm-dispatcher: req:2 'down' [em3]: start running ordered scripts...
localhost NetworkManager[14060]: <info>  [1552637774.4535] device (em3): state change: disconnected -> prepare (reason 'none') [30 40 0]
localhost NetworkManager[14060]: <info>  [1552637774.4543] device (em3): state change: prepare -> config (reason 'none') [40 50 0]
localhost NetworkManager[14060]: <info>  [1552637774.4779] device (em3): state change: config -> ip-config (reason 'none') [50 70 0]
localhost NetworkManager[14060]: <info>  [1552637774.4787] dhcp4 (em3): activation: beginning transaction (timeout in 45 seconds)
localhost NetworkManager[14060]: <info>  [1552637774.4823] dhcp4 (em3): dhclient started with pid 14582
0

I realize using cat /proc/net/dev that there were some network exchanges on em4. I then remembered that when the server was physically installed the 2 Gb ports were connected. So I unplugged the internet cable connected to em4 and my issue seems to be now solved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.