linux 服务重启失败,Linux 重启network 失败的解决办法

本文记录了一次解决Linux系统中network.service服务启动失败的问题过程。通过查看日志发现错误信息,定位到不存在的网络接口eth1和eth2,最终通过删除相关配置文件并重启网络服务解决问题。

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

执行 systemctl restart network 失败

[root@ceph0 ~]# 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@ceph0 ~]# systemctl status network

● 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 二 2019-03-26 12:02:46 CST; 8s ago

Docs: man:systemd-sysv-generator(8)

Process: 3185106 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 network[3185106]: RTNETLINK answers: File exists

3月 26 12:02:46 ceph0 systemd[1]: network.service: control process exited, code=exited status=1

3月 26 12:02:46 ceph0 systemd[1]: Failed to start LSB: Bring up/down networking.

3月 26 12:02:46 ceph0 systemd[1]: Unit network.service entered failed state.

3月 26 12:02:46 ceph0 systemd[1]: network.service failed.

看红色部门 Failed to start LSB: Bring up/down networking. 但是实际上这个信息并没有什么卵用

8f6c268f1c53f5da0717bae074303d47.png

要是你拿着这个信息不假思索的去网上搜一圈,我相信你有可能失望而归。CSDN 等博客都是你抄我,我抄你,从来都不验证下的,就是复制粘贴。

排查思路

遇到这种问题,最好的办法就是看日志输出了啥咯,执行 tail -f /var/log/messages|grep network

[root@ceph0 ~]# tail -f /var/log/messages|grep network

Mar 26 12:05:06 ceph0 systemd: Starting LSB: Bring up/down networking...

Mar 26 12:05:06 ceph0 network: Bringing up loopback interface: [ OK ]

Mar 26 12:05:06 ceph0 network: Bringing up interface eth0: [ OK ]

Mar 26 12:05:06 ceph0 network: Bringing up interface eth1: Error: Connection activation failed: No suitable device found for this connection.

Mar 26 12:05:06 ceph0 network: [FAILED]

Mar 26 12:05:06 ceph0 network: Bringing up interface eth2: Error: Connection activation failed: No suitable device found for this connection.

Mar 26 12:05:06 ceph0 network: [FAILED]

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 network: RTNETLINK answers: File exists

Mar 26 12:05:06 ceph0 systemd: network.service: control process exited, code=exited status=1

Mar 26 12:05:06 ceph0 systemd: Failed to start LSB: Bring up/down networking.

Mar 26 12:05:06 ceph0 systemd: Unit network.service entered failed state.

Mar 26 12:05:06 ceph0 systemd: network.service failed.

可以看到报错

Mar 26 12:05:06 ceph0 network: Bringing up interface eth1: Error: Connection activation failed: No suitable device found for this connection.

Mar 26 12:05:06 ceph0 network: [FAILED]

Mar 26 12:05:06 ceph0 network: Bringing up interface eth2: Error: Connection activation failed: No suitable device found for this connection.

很明显,没有eth1 和eth2 接口 导致报错,进入 /etc/sysconfig/network-scripts/

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

[root@ceph0 network-scripts]# ls

ifcfg-eth0 ifdown-eth ifdown-post ifdown-tunnel ifup-ippp ifup-post ifup-tunnel

ifcfg-eth1 ifdown-ib ifdown-ppp ifup ifup-ipv6 ifup-ppp ifup-wireless

ifcfg-eth2 ifdown-ippp ifdown-routes ifup-aliases ifup-isdn ifup-routes init.ipv6-global

ifcfg-lo ifdown-ipv6 ifdown-sit ifup-bnep ifup-ovs ifup-sit network-functions

ifdown ifdown-isdn ifdown-Team ifup-eth ifup-plip ifup-Team network-functions-ipv6

ifdown-bnep ifdown-ovs ifdown-TeamPort ifup-ib ifup-plusb ifup-TeamPort

[root@ceph0 network-scripts]#

删除eth1 和eth2 配置文件,重启网卡即可

root@ceph0 network-scripts]# rm -rf ifcfg-eth1 ifcfg-eth2

[root@ceph0 network-scripts]# systemctl restart network

[root@ceph0 network-scripts]#

6ad3dd87ede1e54bf6059c80e9f2384a.png

### 解决Linux系统中网络服务重启失败的方法 对于Linux系统中的网络服务重启失败问题,可以通过一系列诊断措施来找出根本原因并加以修复。 #### 1. 检查系统日志 当遇到任何类型的启动或重启问题时,应当优先查阅系统日志以获取更多信息。这有助于了解是否存在硬件错误或者软件冲突等问题。通过`dmesg`命令能够访问到最新的内核环缓冲区消息,其中包含了自上次引导以来的重要事件记录[^1]: ```bash $ dmesg | grep -i network ``` 此外,还可以利用专门的日志工具如`journalctl`来查看更详细的日志条目,特别是针对特定的服务单元(例如network.service): ```bash $ journalctl -u NetworkManager --since today ``` #### 2. 验证配置文件设置 如果怀疑是由于配置当引起的故障,则需仔细审查相关的配置文件。对于基于Red Hat的企业级发行版而言,通常可以在路径`/etc/sysconfig/network-scripts/`下找到接口的具体设定;比如编辑名为ifcfg-eth0的文件就可以调整Ethernet适配器的相关参数[^3]: ```bash sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0 ``` 确保所有必要的字段都已正确定义,并且没有任何语法上的失误。常见的选项包括但限于IPADDR, NETMASK 和 GATEWAY等。 #### 3. 测试基本连通性和功能 为了进一步确认问题是出自本地还是外部因素,在执行其他操作之前建议先做简单的ping测试以及尝试手动激活网卡设备: ```bash # Ping默认网关或其他可信赖的目标主机 ping www.example.com # 使用ip link set 命令启用指定的网络接口 sudo ip link set eth0 up ``` 这些基础性的验证可以帮助排除一些显而易见的可能性,从而缩小排查范围。 #### 4. 尝试重启整个系统 假如经过上述努力仍然无法恢复正常运作状态的话,那么最后的选择就是考虑完全关闭再开机重置一次环境。有时这样做足以清除某些瞬态条件下的障碍物,使得一切恢复原状[^2]。 ```bash sudo reboot now ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值