Find knowledge base article(s) by searching for keywords in the title e.g. type linux in the search box below
Find knowledge base article(s) by browsing the subject categories of articles
Technology quick references, cheatsheets, user manuals etc.
Shop Online through ShopifyLite
Tutorials on various IT applications.
Search Title    (UL:0 |SS:f)

Software >> OS >> Unix >> Linux >> RHEL >> 7 >> Network >> How to fix issue of systemctl restart network failed due to - Failed to start LSB: Bring up down network - error

Make sure there are no redundant ifcfg-* scripts in /etc/sysconfig/network-scripts/ directory

Error

[root@rhel7client1 ~]# systemctl restart network
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.

[root@rhel7client1 ~]# systemctl status network.service
● 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 Tue 2020-06-16 21:51:10 +08; 36s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3334 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 network[3334]: RTNETLINK answers: File exists
Jun 16 21:51:10 rhel7client1 systemd[1]: network.service: control process exited, code=exited status=1
Jun 16 21:51:10 rhel7client1 systemd[1]: Failed to start LSB: Bring up/down networking.
Jun 16 21:51:10 rhel7client1 systemd[1]: Unit network.service entered failed state.
Jun 16 21:51:10 rhel7client1 systemd[1]: network.service failed.

 

Check #1

 

[root@rhel7client1 network-scripts]# cd /etc/sysconfig/network-scripts

 

[root@rhel7client1 network-scripts]# ls -ld ifcfg-*

-rw-r--r--. 1 root root 289 Jun 16 20:31 ifcfg-enp0s3
-rw-r--r--. 1 root root 254 Aug 19  2019 ifcfg-lo
-rw-r--r--. 1 root root 322 Jun 16 20:27 ifcfg-Wired_connection_1
-rw-r--r--. 1 root root 292 Jun 16 20:31 ifcfg-Wired_connection_1-1

[root@rhel7client1 network-scripts]# grep HWADDR ifcfg-Wired*
ifcfg-Wired_connection_1:HWADDR=08:00:27:60:57:5B
ifcfg-Wired_connection_1-1:HWADDR=08:00:27:94:21:02

remove the invalid ifcfg-* script

[root@rhel7client1 network-scripts]# rm ifcfg-Wired_connection_1

Check #2

Make sure interfaces configured for automatic IP address have DHCP to assign IP, else change to manual before activating

e.g.

root@rhel7client1 ~]# nmcli con up enp0s8
Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)

[root@rhel7client1 ~]# nmcli con mod enp0s8 ipv4.addresses "192.168.0.20/24"
[root@rhel7client1 ~]# nmcli con mod enp0s8 ipv4.method manual
[root@rhel7client1 ~]# nmcli con up enp0s8
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/11)

 

 

[ © 2008-2021 myfaqbase.com - A property of WPDC Consulting ]