I've been reading around for a couple of days and looking for a solution to a network problem but to no avail.
I'm running CentOS 7.7.1908 with kernel 3.10.0-1062.4.1.el7.x86_64 and I use NetworkManager. The IP address is assigned from a DHCP Server. Moreover, we have two nfs volumes that we mount.
When booting I see:
and later on[FAILED] Failed to start LSB: Bring up/down networking.
[FAILED] Failed to mount /import/hlohomes.
See 'systemctl status import-hlohomes.mount' for details.
[FAILED] Failed to mount /import/hlodata.
See 'systemctl status import-hlodata.mount' for details.
Once logged in systemctl --failed gives:
Code: Select all
UNIT LOAD ACTIVE SUB DESCRIPTION ● import-hlodata.mount loaded failed failed /import/hlodata ● import-hlohomes.mount loaded failed failed /import/hlohomes ● network.service loaded failed failed LSB: Bring up/down networking
The ifcfg-eno1 file in /etc/sysconfig/network-scripts is:Active: failed (Result: exit-code) since Thu 2019-10-24 12:56:35 CEST; 50min ago
Process: 2230 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Oct 24 12:56:35 pcname.Domain.DE systemd: Starting LSB: Bring up/down networking...
Oct 24 12:56:35 pcname.Domain.DE network: Bringing up loopback interface: [ OK ]
Oct 24 12:56:35 pcname.Domain.DE network: Bringing up interface eno1: Error: Connection activation failed: No suitable device found for this connection (device eno1 not available because device has no carrier).
Oct 24 12:56:35 pcname.Domain.DE network: [FAILED]
Oct 24 12:56:35 pcname.Domain.DE systemd: network.service: control process exited, code=exited status=1
Oct 24 12:56:35 pcname.Domain.DE systemd: Failed to start LSB: Bring up/down networking.
Oct 24 12:56:35 pcname.Domain.DE systemd: Unit network.service entered failed state.
Oct 24 12:56:35 pcname.Domain.DE systemd: network.service failed.
running nmcli connection show gives# Generated by dracut initrd
Code: Select all
NAME UUID TYPE DEVICE eno1 d9ef6661-d6b7-45c8-a934-f2c49e9bf4b0 ethernet eno1 virbr0 4493b9ac-f204-420e-85ed-5f7589aa1a1d bridge virbr0 enp11s0 6f3748cf-e30c-b688-a386-339eea9ff7f3 ethernet --
Once booted, the computer is on the network, even though the network service is in a failed state.
The strange thing is, we have several other computers with identical configurations (except UUID obviosuly) which do not show this kind of behavior.
In case this helps to identify the problem: I once assigned a different MAC Address to this computer in the Gnome-GUI of NetworkManager and when I changed it back to the original MAC address these problems started to occur.
I included a HWADDR line in the ifcfg file and rebooted, I generated a new UUID, specified it in the ifcfg file and rebooted. None fixed the problem. I even disabled NetworkManager ... however, in this scenario the computer didn't end up in the network and I had to login locally and do systemctl restart network. When I move the ifcfg file to /root/ and reboot, the error does not show up. However, the nfs volumes still fail to be mounted. I can achieve that the nfs mounts are mounted by adding
in the respective line in /etc/fstabcomment=systemd.automount
but during boot time I still get failed mount attempts for these.
Personally, I think the closest I can trace back the problem is somewhat connected to
but I just do not know what this is supposed to tell me. I assume that later on, i.e. when NetworkManager successfully connects to the network, the device has a carrier.Bringing up interface eno1: Error: Connection activation failed: No suitable device found for this connection (device eno1 not available because device has no carrier
Any help and suggestions are appreciated!