CentOS 7 下网络无法访问 Failed to start LSB: Bring up/.
[root@localhost Desktop]# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.067 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.065 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.079 ms
^C
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 0.065/0.070/0.079/0.009 ms
[root@localhost Desktop]# ping www.baidu.com
ping: unknown host www.baidu.com
[root@localhost Desktop]# route add default gw 192.168.2.1
[root@localhost Desktop]# 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@localhost Desktop]# 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 Thu 2017-08-17 19:13:34 PDT; 2min 13s ago
Docs: man:systemd-sysv-generator(8)
Process: 3688 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain network[3688]: RTNETLINK answers: File exists
Aug 17 19:13:34 localhost.localdomain systemd[1]: network.service: control proce...1
Aug 17 19:13:34 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/....
Aug 17 19:13:34 localhost.localdomain systemd[1]: Unit network.service entered f....
Aug 17 19:13:34 localhost.localdomain systemd[1]: network.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@localhost Desktop]# clear
[3;J
[root@localhost Desktop]# systemctl stop NetworkManager
[root@localhost Desktop]# systemctl disable NetworkManager
Removed symlink /etc/systemd/system/multi-user.target.wants/NetworkManager.service.
Removed symlink /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service.
Removed symlink /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service.
[root@localhost Desktop]# systemctl start network.service
[root@localhost Desktop]# ping www.baidu.com
PING www.a.shifen.com (111.13.100.91) 56(84) bytes of data.
64 bytes from 111.13.100.91: icmp_seq=1 ttl=51 time=20.8 ms
64 bytes from 111.13.100.91: icmp_seq=2 ttl=51 time=21.0 ms
64 bytes from 111.13.100.91: icmp_seq=3 ttl=51 time=22.2 ms
64 bytes from 111.13.100.91: icmp_seq=4 ttl=51 time=21.6 ms
64 bytes from 111.13.100.91: icmp_seq=5 ttl=51 time=21.6 ms
64 bytes from 111.13.100.91: icmp_seq=6 ttl=51 time=21.4 ms
64 bytes from 111.13.100.91: icmp_seq=7 ttl=51 time=21.2 ms
64 bytes from 111.13.100.91: icmp_seq=8 ttl=51 time=21.7 ms
64 bytes from 111.13.100.91: icmp_seq=9 ttl=51 time=52.0 ms
64 bytes from 111.13.100.91: icmp_seq=10 ttl=50 time=26.7 ms
64 bytes from 111.13.100.91: icmp_seq=11 ttl=50 time=24.9 ms
64 bytes from 111.13.100.91: icmp_seq=12 ttl=50 time=22.9 ms
64 bytes from 111.13.100.91: icmp_seq=13 ttl=50 time=27.9 ms
64 bytes from 111.13.100.91: icmp_seq=14 ttl=50 time=45.3 ms
64 bytes from 111.13.100.91: icmp_seq=15 ttl=50 time=54.8 ms
64 bytes from 111.13.100.91: icmp_seq=16 ttl=50 time=51.8 ms
64 bytes from 111.13.100.91: icmp_seq=17 ttl=50 time=32.6 ms
64 bytes from 111.13.100.91: icmp_seq=18 ttl=50 time=22.2 ms
64 bytes from 111.13.100.91: icmp_seq=19 ttl=50 time=22.9 ms
64 bytes from 111.13.100.91: icmp_seq=20 ttl=50 time=25.4 ms
64 bytes from 111.13.100.91: icmp_seq=21 ttl=50 time=23.0 ms
64 bytes from 111.13.100.91: icmp_seq=22 ttl=50 time=30.3 ms
64 bytes from 111.13.100.91: icmp_seq=23 ttl=50 time=25.2 ms
^C64 bytes from 111.13.100.91: icmp_seq=24 ttl=50 time=33.6 ms
--- www.a.shifen.com ping statistics ---
24 packets transmitted, 24 received, 0% packet loss, time 222495ms
rtt min/avg/max/mdev = 20.851/28.921/54.831/10.573 ms
You have new mail in /var/spool/mail/root
[root@localhost Desktop]#
CentOS 7 下网络无法访问 Failed to start LSB: Bring up/.的更多相关文章
- CentOS 7.2重启网络报错 Failed to start LSB: Bring up/down
CentOS 7.2重启网络报错 Failed to start LSB: Bring up/down 我的虚拟机原本有两块网卡,一块叫eno16777736,另一块叫eno5033674.本来是正常 ...
- Centos7 网络出错(failed to start LSB: Bring up/down networking )
这是我更换了VM虚拟机内存,重启后无法连接网络. 然后这是因为NetworkManager.service这个程序造成 解决方法: systemctl disable NetworkManager.s ...
- Redhat中网络启动错误解决办法( Failed to start LSB: Bring up/down networking RTNETLINK answers: File exists)
关于Redhat系列中网络启动失败的解决办法 报错: Failed to start LSB: Bring up/down networking. RTNETLINK answ ...
- Failed to start LSB: Bring up/down错误解决方法
很多朋友在使用centos7系统时,有时候需要分配多个IP地址,这就涉及到修改网卡配置,但是在修改完网卡配置时,重启网络服务时会出现"Failed to start LSB: Bring u ...
- CentOS7 Failed to start LSB: Bring up/down解决方法
刚刚装好的虚拟机突然不能上网了,报错很诡异,具体报错如下: /etc/init.d/network restart Restarting network (via systemctl): Job f ...
- code=exited,status=1/failure;failed to start LSB:Bring up/down networking
环境: CentOS 7 vmware 12 操作: 复制可使用的vmware centOS 7系统至新环境 问题: 无法启动网络 查看“systemctl status network" ...
- Failed to start LSB: Bring up/down networking.
由于我的虚拟机是从别的机器拷贝过来的,导入新机器后,没有问题,第二天就网络连接不上了,就出现下面的错误 [root@centos ~]# /etc/init.d/network restart Res ...
- CentOS7 Failed to start LSB: Bring up/down
原文地址:http://addam.blog.51cto.com/5041993/1839518 刚刚装好的虚拟机突然不能上网了,报错很诡异,具体报错如下: /etc/init.d/network r ...
- CentOS7 Failed to start LSB: Bring up/down解决方法(真正有效的方法)
刚刚装好的虚拟机突然不能上网了,报错很诡异,具体报错如下: /etc/init.d/network restart Restarting network (via systemctl): Job f ...
随机推荐
- npm包开发与发布
把通用的功能开发成npm包,便用使用和维护,更重要的是可以分享给广大的开发者,是不是很激动人心! 那么,步骤如下: 1.创建项目 创建项目目录,npm init ,根据需要输入配置信息(建完后也可以在 ...
- [ubuntu][deepin]系统增加自定义开机启动项
[ubuntu][deepin]系统增加自定义开机启动项 进行配置 cd /etc/init.d/ ls vim myScript nginx实例 #! /bin/sh # chkconfig: # ...
- 富文本编辑器TinyMCE的使用(React Vue)
富文本编辑器TinyMCE的使用(React Vue) 一,需求与介绍 1.1,需求 编辑新闻等富有个性化的文本 1.2,介绍 TinyMCE是一款易用.且功能强大的所见即所得的富文本编辑器. Tin ...
- LeetCode——409. Longest Palindrome
题目: Given a string which consists of lowercase or uppercase letters, find the length of the longest ...
- 工作中常见的五种技术leader
力不从心型 在工作中有种技术leader,总认为自己是最好的.在方案设计的时候,自己有一种方案,下属有一种方案.leader非要别人听他的.如果两种方案没有优劣之分,比较建议的做法是让真正实施的人按照 ...
- Django2.2中间件详解
中间件是 Django 用来处理请求和响应的钩子框架.它是一个轻量级的.底层级的"插件"系统,用于全局性地控制Django 的输入或输出,可以理解为内置的app或者小框架. 在dj ...
- 记录一次Git解决CONFLICT冲突
目录 记录一次Git解决CONFLICT冲突 1.CONFLICT产生的原因 2.Git正确的LIANGZHONG 使用流程 2.1 暂存,拉取,恢复暂存,合并(如果有冲突),提交,推送 2.2 将本 ...
- 100天搞定机器学习|day43 几张GIF理解K-均值聚类原理
前文推荐 如何正确使用「K均值聚类」? KMeans算法是典型的基于距离的聚类算法,采用距离作为相似性的评价指标,即认为两个对象的距离越近,其相似度就越大.该算法认为簇是由距离靠近的对象组成的,因此把 ...
- js 事件发布订阅销毁
在vue中 通过$on订阅事件,通过$emit触发事件以此可用来事件跨组件传值等功能,但是有个弊端就是通过这种方式订阅的事件可能会触发多次. 特别是通过$on订阅的事件中如果有http请求,将会造成触 ...
- 基于ZooKeeper的三种分布式锁实现
[欢迎关注公众号:程序猿讲故事 (codestory),及时接收最新文章] 今天介绍基于ZooKeeper的分布式锁的简单实现,包括阻塞锁和非阻塞锁.同时增加了网上很少介绍的基于节点的非阻塞锁实现,主 ...