今天一台一直在用的虚拟机重启后，CRT连接不上，ip也ping不通，重启网卡报错，“Failed to start LSB: Bring up/down networking”，参考：http://blog.51cto.com/11863547/1905929，解决。

遇到这个错误好几次，所以总结了一下排解的几种方法。

错误记录及排查方法过程：

当我克隆出一台新的centos7的虚拟机的时候，修改了网卡配置文件启动时，报错

[root@centos7 ~]# 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@centos7 ~]#

按照提示输入systemctl status network.service查看

[root@centos7 ~]# systemctl status network.service
● network.service - LSB: Bring up/down networkingLoaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)Active: failed (Result: exit-code) since Mon 2017-03-13 23:24:37 CST; 16s agoDocs: man:systemd-sysv-generator(8)Process: 2878 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 network[2878]: RTNETLINK answers: File exists
Mar 13 23:24:37 centos7 systemd[1]: network.service: control process exited, code=exited status=1
Mar 13 23:24:37 centos7 systemd[1]: Failed to start LSB: Bring up/down networking.
Mar 13 23:24:37 centos7 systemd[1]: Unit network.service entered failed state.
Mar 13 23:24:37 centos7 systemd[1]: network.service failed.

无奈去百度了一下，找到解决方法，说是centos7没有70-persistent-net.rules这个文件，所以新克隆的机器需要配置mac地址。

通过ip a命令查看mac地址是00:0c:29:0c:15:49

2: eno16777736: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000link/ether 00:0c:29:0c:15:49 brd ff:ff:ff:ff:ff:ff

然后在配置文件中加入这一行（如果存在的话只修改就可以）

HWADDR=00:0c:29:0c:15:49

重启生效

[root@centos7 ~]# systemctl restart network.service
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[root@centos7 ~]#

发现依然有这个错误

查看启动日志

Mar 13 23:51:35 centos7 systemd: Starting LSB: Bring up/down networking...
Mar 13 23:51:35 centos7 network: Bringing up loopback interface:  Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Mar 13 23:51:35 centos7 network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Mar 13 23:51:35 centos7 network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Mar 13 23:51:35 centos7 network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Mar 13 23:51:35 centos7 network: [  OK  ]
Mar 13 23:51:36 centos7 network: Bringing up interface eth0:  Error: Connection activation failed: No suitable device found for this connection.
Mar 13 23:51:36 centos7 network: [FAILED]
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 network: RTNETLINK answers: File exists
Mar 13 23:51:36 centos7 systemd: network.service: control process exited, code=exited status=1
Mar 13 23:51:36 centos7 systemd: Failed to start LSB: Bring up/down networking.
Mar 13 23:51:36 centos7 systemd: Unit network.service entered failed state.
Mar 13 23:51:36 centos7 systemd: network.service failed.

发现无法加载/etc/sysconfig/network-scripts/ifcfg-lo文件

给NetworkManager-wait-online服务设置开机自启动

systemctl enable NetworkManager-wait-online.service

然后重启网卡

[root@centos7 ~]# 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@centos7 ~]#

查看日志

Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'

这个错误依然存在

systemctl stop NetworkManager
systemctl disable NetworkManager

将 NetworkManager关闭，然后重启网卡，查看日志

Mar 14 00:31:27 centos7 systemd: Starting LSB: Bring up/down networking...
Mar 14 00:31:27 centos7 network: Bringing up loopback interface:  [  OK  ]
Mar 14 00:31:28 centos7 network: Bringing up interface eth0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization.
Mar 14 00:31:28 centos7 /etc/sysconfig/network-scripts/ifup-eth: Device eth0 does not seem to be present, delaying initialization.
Mar 14 00:31:28 centos7 network: [FAILED]
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 network: RTNETLINK answers: File exists
Mar 14 00:31:28 centos7 systemd: network.service: control process exited, code=exited status=1
Mar 14 00:31:28 centos7 systemd: Failed to start LSB: Bring up/down networking.
Mar 14 00:31:28 centos7 systemd: Unit network.service entered failed state.
Mar 14 00:31:28 centos7 systemd: network.service failed.
Mar 14 00:33:42 centos7 dhclient[3813]: DHCPREQUEST on eno16777736 to 10.0.0.254 port 67 (xid=0x4d17f187)
Mar 14 00:33:42 centos7 dhclient[3813]: DHCPACK from 10.0.0.254 (xid=0x4d17f187)

那个错误已经不见了，但是重启网卡

[root@centos7 ~]# 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@centos7 ~]#

依然是这个错误，然后我又重新百度，说虚拟机设置中的两个连接选项（已连接和启动时连接）没有选择也会报同样的错，但是我的已经连接，问题依然存在，到底是因为什么呢？再次查找方法。

结果这次认真看了日志报错后发现是说eth0这个文件找不到

Mar 14 00:36:39 centos7 network: Bringing up interface eth0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization.
Mar 14 00:36:39 centos7 /etc/sysconfig/network-scripts/ifup-eth: Device eth0 does not seem to be present, delaying initialization.

原来是之前做优化的时候将7的网卡名改成了eth0（众所周知7的网卡名是eno后面随机 一串数字），生成菜单时没有生效，那么在此生效一下

注意网卡配置名是已经修改成eth0以后执行下面操作，一共修改的地方有三处，第一处网卡名：/etc/sysconfig/network-scripts/ifcfg-eth0 ，第二处配置文件里面：NAME=eth0 ，第三处也是配置文件里面：DEVICE=eth0

修改/etc/sysconfig/grub，添加net.ifnames=0 biosdevname=0

[root@centos7 ~]# cat  /etc/sysconfig/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=128M rd.lvm.lv=centos/root rhgb quiet net.ifnames=0 biosdevname=0"
GRUB_DISABLE_RECOVERY="true"
[root@centos7 ~]#

生成菜单

[root@centos7 ~]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-327.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-327.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-8058723e5e754d3aabc51842d9108e3b
Found initrd image: /boot/initramfs-0-rescue-8058723e5e754d3aabc51842d9108e3b.img
done
[root@centos7 ~]#

最后reboot重启

最后登录后正常

转载于:https://www.cnblogs.com/wchw2008/p/10094100.html

【转】【centos】启动网卡报错（Failed to start LSB: Bring up/down networking ）解决办法总结...相关推荐

  1. CentOS7 启动网卡报错 failed to start LSB: Bring up/down networking

    网上百度,发现基本上全是说MAC地址不对.修改/ect/sysconfig/network-xxxx/ifcfg-xxx文件中的HWADDR.照着修改后发现还是报相同错误. 无解- -失效的方法- 最 ...

  2. CentOS7 Failed to start LSB: Bring up/down networking.解决方法

    今天用CentOS7 RDO方式安装Openstack,文档上说要disable NetworkManager, 用 network服务才行. 但是我用 service network start命令 ...

  3. linux重启网卡失败--Failed to start LSB: Bring up/down networking

    想把虚拟机ip改成静态的,遇到这样的报错Failed to start LSB: Bring up/down networking 原因: ifconfig 显示网卡叫ens35,ifcfg-ens3 ...

  4. 网络异常：Failed to start LSB: Bring up/down networking

    一.遇到的问题 1.重启机器后,网络异常报:Failed to start LSB: Bring up/down networking 经常会遇到虚拟机重启后,无法建立服务器远程连接的问题,经排查网络 ...

  5. linux 修改网卡报错xe,启动网卡报错（Failed to start LSB: Bring up/down networking ）解决办法总结...

    Failed to start LSB: Bring up/down networking 遇到这个错误好几次,所以总结了一下排解的几种方法. 错误记录及排查方法过程: 当我克隆出一台新的centos ...

  6. Docker启动失败报错Failed to start Docker Application Container Engine解决方案

    在给一台腾讯云机器安装docker后发现无法启动,总是报错Failed to start Docker Application Container Engine,解决思路分享一下,以免各位童鞋踩坑. ...

  7. 【Linux】centOS 错误记录|无法启动网络Failed to start LSB: Bring up/down networking

    目录 Failed to start LSB: Bring up/down networking Failed to mount /sysroot解决方法 Failed to start LSB: B ...

  8. centos7 network网络服务重启报错failed to start lsb

    network网络服务重启报错failed to start lsb 解决办法: 先看log里哪个网卡没有启动 cat /var/log/messages | grep network 查看网卡mac ...

  9. mycat重启报错Failed to connect to the Wrapper at port解决方法

    mycat重启报错Failed to connect to the Wrapper at port解决方法 参考文章: (1)mycat重启报错Failed to connect to the Wra ...

最新文章

  1. python常用类库_Python常用库
  2. 本博客Matlab、FPGA代码获取方法
  3. jhipster_JHipster入门，第3部分
  4. [转]android ListView详解
  5. guassdb200 single node deployment
  6. 基于Java实现的快速排序
  7. 需求获取常见的方法是进行客户访谈，结合你的实践谈谈会遇到什么问题，你是怎么解决的？...
  8. IT行业里有这么多聪明人，他们之间的区别在哪里？
  9. 【转】项目面试-如何介绍自己的项…
  10. 本周题解(9.12)
  11. fir.im Weekly - 技术人也要苦练“七十二变”
  12. 遇到系统问题，先看OS再看CPU
  13. SMT常见元器件贴片封装名称识别
  14. Micrium 开放了µC/OS-III源代码
  15. 投资理财-合理配置资产结构
  16. 微信开发-业务域名、JS接口安全域名、网页授权域名
  17. [安卓开发] 总结一些android的云测试平台
  18. 中南大学计算机学硕毕业要求,中南大学研究生发表学术论文的规定
  19. 云计算与大数据---21大数据张舒
  20. 哈工大21秋移动互联网复习

热门文章

  1. git合并指定文件到另一分支
  2. 程序员的能力矩阵表【转载自】
  3. 我的程序人生以及一些杂项
  4. iOS中 动态启动图GIF的简单设置 韩俊强的博客
  5. 正则表达式：Pattern 与Matcher
  6. oschina导出博客获取图片
  7. Android－－－Activity 生命周期（三）Stopping Activity Restarting Activity
  8. Android 高级Drawable资源－－－复合Drawable－－－－层Drawable
  9. kotlin使用代码javaClass或class.java报错：unresolved reference
  10. 记一次CPU飙升的问题分析解决思路(转)