【已解决】CentOS 7-无法重启网络，systemctl status network.service报错：code=exited, status=1/FAILURE

最新推荐文章于 2025-02-26 00:53:39 发布

神是念着倒

最新推荐文章于 2025-02-26 00:53:39 发布

阅读量1.5w

点赞数 6

分类专栏： Linux 文章标签： code=exited status=1/FAILURE service network restart

本文链接：https://blog.csdn.net/weixin_38256474/article/details/97766652

版权

Linux 专栏收录该内容

10 篇文章

订阅专栏

本文详细介绍了在CentOS 7.5环境下，通过VMware虚拟机进行网络配置的过程及遇到的问题。针对重启网络服务失败的情况，提供了具体的错误信息分析，并给出了包括检查虚拟机网络适配器设置、修改ifcfg-ens-xx文件在内的解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

环境

宿主机：Windows 10 64_bit
虚拟机：VMware 12
- CentOS 7.5 64_bit

正文

[root@slave1 cyg]# 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@slave1 cyg]# 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 2019-07-30 10:52:23 CST; 25s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 17266 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 network[17266]: RTNETLINK answers: File exists
Jul 30 10:52:23 slave1 systemd[1]: network.service: control process exited, code=...s=1
Jul 30 10:52:23 slave1 systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 30 10:52:23 slave1 systemd[1]: Unit network.service entered failed state.
Jul 30 10:52:23 slave1 systemd[1]: network.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@slave1 cyg]# 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> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:0c:29:dc:e2:aa 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:d7:c9:33 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:d7:c9:33 brd ff:ff:ff:ff:ff:ff

前提确保：
（1）虚拟机设置-网络适配器-配置正确。【我这里是NAT模式】

可重新设置：虚拟机设置-网络适配器，移除，重新添加（NAT模式）。

（2）/etc/sysconfig/network-scripts/ifcfg-ens-xx文件，配置正确。

这个ifcfg-ens-xx中的xx，以ip addr显示的为准，在此是ifcfg-ens33。

[root@slave1 zookeeper-3.4.5]# ip addr
....
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:dc:e2:aa brd ff:ff:ff:ff:ff:ff
    inet 192.168.172.11/24 brd 192.168.172.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fedc:e2aa/64 scope link 
       valid_lft forever preferred_lft forever
...

例如：

[root@slave1 zookeeper-3.4.5]# cat /etc/sysconfig/network-scripts/ifcfg-ens33
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="static"
IPADDR=192.168.172.11
NETMASK=255.255.255.0
GATEWAY=192.168.172.2
DNS1=114.114.114.114
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="d11d791b-4b2a-4f8d-b2a3-32b0a8d281d6"
DEVICE="ens33"
HWADDR="00:0c:29:dc:e2:aa"
ONBOOT="yes"