Solved Server (network) does not come back up again after sudden stop of responding

Richard G

Richard G

Verified User
Joined
Jul 6, 2008
Messages
14,149
Location
Maastricht
2 days ago, I removed the NetworkManager and installed network-scripts because NetworkManager messed up the resolv.conf file.
I restarted the startips service and all seemd to keep working fine.

Today suddenly server does not respond to pings anymore.
Nothing is working.
When placing server in rescue mode, the ethernet device does not come up.

I see this in the logs from when the system boots:
Code: 
Feb 10 19:35:24 server kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Feb 10 19:35:24 server systemd-udevd[598]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 10 19:35:24 server systemd-udevd[597]: Using default interface naming scheme 'rhel-8.0'.
Feb 10 19:35:24 server systemd-udevd[597]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 10 19:35:24 server kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0

So I put this line in the /etc/sysconfig/network-scripts/enp2s0 file:
Code: 
ETHTOOL_OPTS="speed 1000 duplex full autoneg on"
which made no difference at all. Network still does not come up.

I don't have a clue on to why suddenly the network stopped working, but since the rescue system works, network card must work too.

Does anybody have a clue on how I can fix this so the network will start at boot again?
 
Very odd.
In spite of the fact that I set NM_CONTROLLED="no" in the network script and install network-scripts, still the network did not came up.

For future references is somebody runs into this problem after uninstalling NetworkManager, then go into rescue system.
Mount your filesystem, chroot it and then you should be able to use yum (or apt) again.
Install NetworkManager again and you should be up and running again.
With many thanks to my friend @bdacus01 for assisting me finding the solution to this! (y)


However, I now still wonder as to how it can happen that it runs for 2 days in a row without issues and then suddenly stops working. Could this have been a DA license check which restarted the network or something like that?
 
Last edited:
in case you want to edit your networkmanager settings,
and not sure what and how to configure it,
simply use the tool "nmtui" as root.
you can configure your interfaces, ip settings, including DNS servers.
 
Thank you.
I know about nmtui, but I just don't like NetworkManager, I'm used to using the old method, so that's why I uninstalled it at first.
 
You must log in or register to reply here.
Back
Top