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.
[root@centOS ~]# systemctl status network.service
[root@centOS ~]# journalctl -xe[root@centOS ~]# systemctl start network.service
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.
[root@centOS ~]# systemctl status network.service
[root@centOS ~]# journalctl -xe
Reason.
On CentOS system, there are currently two network management tools, NetworkManager and network. If both are configured, it will cause conflicts, and NetworkManager will clean up the routes when the network is disconnected. If some custom routes, which are not added to NetworkManager’s configuration file, the routes are cleaned up and need to be custom added on after the network is connected.
Solution.
1. Stop the networkmanager service
systemctl stop NetworkManager
systemctl disable NetworkManager
2. restart the network card, it is OK
systemctl restart network
systemctl status network
Read More:
- [Solved] Job for network.service failed because the control process exited with error code. See “systemctl st
- Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code
- Centos8 Could not restart the Network: Failed to restart network.service: Unit network.service not found
- Linux Connect Error: network.service failed [How to Solve]
- [Solved] Service network restart reported an error and failed to restart
- Service network restart reported an error and failed to restart [How to Solve]
- [Solved] docker Startup Error: Job for docker.service failed because the control process exited with error code
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- [Solved] Job for docker.service failed because the control process exited with error code. After changing the docker configuration
- [Solved] FTP Setup Error: Job for vsftpd.service failed because the control process exited with error code…
- [Solved] KVM Failed to Startup Error: error: Network not found: no network with matching name ‘default‘
- [Solved] Virtual machine Failed to restart network Error: Error:Failed to start LSB: Bring up/down networking
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- [Solved] CentOS Network Card startup error: RTNETLINK answers: File exist
- [FAILED] Failed to start Raise network interfaces
- [Solved] Linux Service Start Error: *.service: Main process exited, code=exited, status=203/EXEC
- Failed to start firewalld.service: Unit is masked [How to Solve]
- Virtual machine ping Command Error: ping name or service not known
- [Solved] Window Redis Service Failed to Startup: bind No error
- Linux system service command error: Failed to allocate directory watch: Too many open files