Job for network.service failed because the control process exited with error code问题
2019年09月28日 12:11:16 fager阅读数 0
今天在centOS 7下更改完静态ip后发现network服务重启不了，翻遍了网络，尝试了各种方法，终于解决了。
现把各种解决方法归纳整理，希望能让后面的同学少走点歪路。。。
首先看问题：执行service network restart命令后出现下面的错误：
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. [失败]
根据提示输入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 五 2017-07-14 19:01:47 CST; 1min 16s ago
Docs: man:systemd-sysv-generator(8)
Process: 4681 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
CGroup: /system.slice/network.service
└─1192 /sbin/dhclient -H mini1 -1 -q -lf /var/lib/dhclient/dhclient–ens33.lease -pf /v…
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 network[4681]: RTNETLINK answers: File exists
7月 14 19:01:47 mini1 systemd[1]: network.service: control process exited, code=exited status=1
7月 14 19:01:47 mini1 systemd[1]: Failed to start LSB: Bring up/down networking.
7月 14 19:01:47 mini1 systemd[1]: Unit network.service entered failed state.
7月 14 19:01:47 mini1 systemd[1]: network.service failed.
network服务启动不了首先保证/etc/sysconfig/network-scripts目录下的ifcfg-xxx（每台机器不一定相同）没有错误（如果你改动过的话），这里的错误指的在更改过程中因为手误敲错字母之类的。
网上最常见的几种做法如下：
1.和 NetworkManager 服务有冲突，这个好解决，直接关闭 NetworkManger 服务就好了， service NetworkManager stop，并且禁止开机启动 chkconfig NetworkManager off 。之后重启就好了。
2和配置文件的MAC地址不匹配，这个也好解决，使用ip addr（或ifconfig）查看mac地址
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:b8:e7:21 brd ff:ff:ff:ff:ff:ff
inet 192.168.65.141/24 brd 192.168.65.255 scope global dynamic ens33
valid_lft 1193sec preferred_lft 1193sec
inet6 fe80::cca2:d835:f93:e637/64 scope link
valid_lft forever preferred_lft forever
00:0c:29:b8:e7:21这个就是MAC地址了，将/etc/sysconfig/network-scripts/ifcfg-xxx中的HWADDR（如果没有就添加上）改成这个MAC地址
3.设定开机启动一个名为NetworkManager-wait-online服务，命令为：
systemctl enable NetworkManager-wait-online.service
=========================================================================================================
上面两个是我看到最多的解决方法，但是很遗憾，我的并没有解决。
有查看资料，发现了以下一些方法：
4.查看/etc/sysconfig/network-scripts下，将其余无关的网卡位置文件全删掉，避免不必要的影响，即只留一个以ifcfg开头的文件，
留的那一个应和使用ip addr命令查看ip第二条开头的名称一致（我的是ens33，参见上面我贴出的ip addr命令执行结果），所以我只留了一个ifcfg-ens33。（我的其中两台机器就是这么弄好的，因为我在修改前留了备份，把备份删掉就好了。。。）
5.将ifcfg-xxx文件中的DEVICE一行注释掉。
6.将ifcfg-xxx中的NAME改为和文件名一致。
7.在VMWare的编辑-虚拟网络编辑器中将网络模式改为桥接。
8.看VMWare右下角的网络适配器是否连接，如果没有连接则连接上。
（补充：点击网络适配器-设置，将NAT模式改为桥接试试，我的改为桥接后可以重启network服务了但是上不了网，可以重启后
再将桥接模式改为NAT模式，发现既可以上网又可以重启network服务了）
9.查看下你电脑有没有禁用了VMware DHCP service和VMware NAT service 这几个vm服务，如果禁用则开启。
10 .如果你改成了静态ip别忘了将BOOTPROTO改为static。
11.如果以上都没有解决，还有最后一招-- 重启 看一看有没有奇迹发生！！（我的另外一台重启后莫名就好了）
上面这些方法，我基本都试过了，对我的机器有的有用有的没用，但是有人也用这些方法解决了，所以一并记录下来。希望能给予你一点帮助微笑
#参见https://blog.csdn.net/u014466635/article/details/80284792
和
https://blog.csdn.net/dongfei2033/article/details/81124465
yxf@master ~]$ su root
Password:
[root@master yxf]# vi /etc/sysc
sysconfig/ sysctl.conf sysctl.d/
[root@master yxf]# vi /etc/sysconfig/network-scripts/ifcfg-eth0
[root@master yxf]# vi /etc/sysconfig/network-scripts/ifcfg-e
ifcfg-ens33 ifcfg-eth0
[root@master yxf]# vi /etc/sysconfig/network-scripts/ifcfg-ens33
[root@master yxf]# service network restart
Restarting network (via systemctl): ehJob for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[FAILED]
[root@master yxf]# service network restart
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]
[root@master yxf]# 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 Wed 2016-09-28 11:47:57 CST; 1min 23s ago
Docs: man:systemd-sysv-generator(8)
Process: 12112 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master network[12112]: RTNETLINK answers: File exists
Sep 28 11:47:57 master systemd[1]: network.service: control process exited, code=...s=1
Sep 28 11:47:57 master systemd[1]: Failed to start LSB: Bring up/down networking.
Sep 28 11:47:57 master systemd[1]: Unit network.service entered failed state.
Sep 28 11:47:57 master systemd[1]: network.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@master yxf]# cd /etc/sysconfig/network-scripts/
[root@master network-scripts]# ls
ifcfg-ens33 ifdown-ipv6 ifdown-tunnel ifup-isdn ifup-TeamPort
ifcfg-eth0 ifdown-isdn ifup ifup-plip ifup-tunnel
ifcfg-lo ifdown-post ifup-aliases ifup-plusb ifup-wireless
ifdown ifdown-ppp ifup-bnep ifup-post init.ipv6-global
ifdown-bnep ifdown-routes ifup-eth ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ib ifup-routes network-functions-ipv6
ifdown-ib ifdown-Team ifup-ippp ifup-sit
ifdown-ippp ifdown-TeamPort ifup-ipv6 ifup-Team
[root@master network-scripts]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:f4:c9:30 brd ff:ff:ff:ff:ff:ff
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:da:b6:29 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:da:b6:29 brd ff:ff:ff:ff:ff:ff
[root@master network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-eth0
[root@master network-scripts]# service network restart
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]
[root@master network-scripts]# ls
ifcfg-ens33 ifdown-ipv6 ifdown-tunnel ifup-isdn ifup-TeamPort
ifcfg-eth0 ifdown-isdn ifup ifup-plip ifup-tunnel
ifcfg-lo ifdown-post ifup-aliases ifup-plusb ifup-wireless
ifdown ifdown-ppp ifup-bnep ifup-post init.ipv6-global
ifdown-bnep ifdown-routes ifup-eth ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ib ifup-routes network-functions-ipv6
ifdown-ib ifdown-Team ifup-ippp ifup-sit
ifdown-ippp ifdown-TeamPort ifup-ipv6 ifup-Team
[root@master network-scripts]# vi ifcfg-eth0
[root@master network-scripts]# rm -rf ifcfg-eth0
[root@master network-scripts]# ls
ifcfg-ens33 ifdown-isdn ifup ifup-plip ifup-tunnel
ifcfg-lo ifdown-post ifup-aliases ifup-plusb ifup-wireless
ifdown ifdown-ppp ifup-bnep ifup-post init.ipv6-global
ifdown-bnep ifdown-routes ifup-eth ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ib ifup-routes network-functions-ipv6
ifdown-ib ifdown-Team ifup-ippp ifup-sit
ifdown-ippp ifdown-TeamPort ifup-ipv6 ifup-Team
ifdown-ipv6 ifdown-tunnel ifup-isdn ifup-TeamPort
[root@master network-scripts]# vi ifcfg-ens33
[root@master network-scripts]# service network restart
Restarting network (via systemctl): [ OK ]
[root@master network-scripts]# ping 192.168.0.104
PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data.
64 bytes from 192.168.0.104: icmp_seq=1 ttl=128 time=0.735 ms
64 bytes from 192.168.0.104: icmp_seq=2 ttl=128 time=0.673 ms
64 bytes from 192.168.0.104: icmp_seq=3 ttl=128 time=0.610 ms
64 bytes from 192.168.0.104: icmp_seq=4 ttl=128 time=0.623 ms
64 bytes from 192.168.0.104: icmp_seq=5 ttl=128 time=0.632 ms
^C
--- 192.168.0.104 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.610/0.654/0.735/0.053 ms
[root@master network-scripts]#
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="static"
#BOOTPROTO="dhcp"
HWADDR="00:0c:29:f4:c9:30"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="ens33"
UUID="5e5ec170-b882-4620-97fb-7b421a4ba945"
DEVICE="ens33"
ONBOOT="yes"
IPADDR="192.168.11.100"
NETMASK="255.255.255.0"
GATEWAY="192.168.11.1"
~
~
~
~
~
"ifcfg-ens33" 20L, 428C
