Comments 11 Posted In Red Hat OpenStack Platform failed to start lsb bring up/down networking rhel 7 Latest response 2019-10-10T04:51:33+00:00 Restarting network (via systemctl): Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details. [FAILED] sk Started 2016-03-30T14:27:00+00:00 by sellini khoulou Newbie 14 points Log in to join the conversation Responses Sort By Oldest Sort By Newest RN Newbie 7 points 6 June 2017 1:37 PM Robert Neary I have the same issue on a fresh RHEL 7 install AY Newbie 5 points 6 June 2017 5:22 PM Albert Yandow Same here: Failed to start LSB: Bring up/down networking. SM Guru 4790 points 7 June 2017 10:51 AM Sadashiva Murthy M What does "systemctl status network" shows up? Check if this helps https://access.redhat.com/solutions/2784681 GJ Newbie 7 points 9 November 2017 5:17 PM Gary Jarrell I am seeing the same issue, but it only occurs when I add NM_CONTROLLED="no" to my ifcfg-bond1 file. If I remove it, it works fine. SM Guru 4790 points 10 November 2017 6:35 AM Sadashiva Murthy M That is expected behavior, since by default NetworkManager takes the lead in activating/controlling network interfaces in RHEL7.x systems. Is NetworkManager disabled over there? Is this RHEL7.x? SC Newbie 7 points 10 September 2018 9:32 AM Shahdat Chowdhury getting error in RHEL 7.4 : failed to start lsb bring up/down networking ES Newbie 17 points 25 October 2018 10:47 PM Edgar R. Sampere Romero Same here but checking other posts it's caused because NetworkManager starts before the interface is ready. I I've been reading it does not affect the network unit, however it messes my wireless connection don't know how or why RC Newbie 16 points 13 December 2018 4:49 PM Robin Coe I just started getting this problem running as a VBox guest running 7.6. I can manually connect the interfaces, one NAT and one Vhost-only, but the network manager fails to start the interfaces. When I run systemctl status network, I get "RTNETLINK answers: File exists". I believe this problem started when I incurred a catastrophic failure in the virtual host guest additions. All was running smoothly until I used the VBox menu to set the virtual display to move to an external monitor. That caused the guest to reboot and from then on, guest additions refuse to allow guest scaling, even after reinstalling guest additions in the RHEL guest, or the network manager to start the interfaces. AH Newbie 15 points 28 February 2019 11:43 PM Amer Hwitat there is a similar solution at: https://communities.vmware.com/thread/580135 MW Newbie 16 points 4 September 2019 3:53 AM Michael Wilcox I had this error due to setting my ethernet interfaces to DHCP when they should be Manual ( ie Static IPs).. ss Newbie 7 points 10 October 2019 4:51 AM shajalal sagor how can fix this problem .