CentOS7 service network start命令启动时报错解决方法

简介: CentOS7 service network start命令启动时报错解决方法

service network start命令启动时报错:


[root@localhost network-scripts]# service network start
Starting network (via systemctl):  Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.[FAILED][root@localhost network-scripts]# systemctl status network.servicenetwork.service - LSB: Bring up/down networking   Loaded: loaded (/etc/rc.d/init.d/network)   Active: failed (Result: exit-code) since Sat 2015-03-07 02:53:12 EST; 6s ago  Process: 8596 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain network[8596]: RTNETLINK answers: File ...Mar 07 02:53:12 localhost.localdomain systemd-sysctl[8913]: Overwriting earli...Mar 07 02:53:12 localhost.localdomain systemd[1]: network.service: control pr...Mar 07 02:53:12 localhost.localdomain systemd[1]: Failed to start LSB: Bring ...Mar 07 02:53:12 localhost.localdomain systemd[1]: Unit network.service entere...Hint: Some lines were ellipsized, use -l to show in full.



然后网上搜是因为没加HWADDR....这个我确实给删了....


先看log里说哪个网卡没有UP起来:


[root@localhost network-scripts]# cat /var/log/messages | grep network


Mar  7 03:05:18 localhost kernel: drop_monitor: Initializing network drop monitor serviceMar  7 03:05:19 localhost systemd-udevd[413]: renamed network interface eth1 to enp1s0f1Mar  7 03:05:19 localhost systemd-udevd[416]: renamed network interface eth5 to enp8s0f3Mar  7 03:05:19 localhost systemd-udevd[421]: renamed network interface eth3 to enp8s0f1Mar  7 03:05:19 localhost systemd-udevd[429]: renamed network interface eth4 to enp8s0f2Mar  7 03:05:19 localhost systemd-udevd[411]: renamed network interface eth0 to enp1s0f0Mar  7 03:05:19 localhost systemd-udevd[419]: renamed network interface eth2 to enp8s0f0Mar  7 03:05:25 localhost systemd-udevd[412]: renamed network interface eth1 to enp3s0f1Mar  7 03:05:25 localhost systemd-udevd[414]: renamed network interface eth3 to enp131s0f1Mar  7 03:05:25 localhost systemd-udevd[411]: renamed network interface eth0 to enp3s0f0Mar  7 03:05:25 localhost systemd-udevd[413]: renamed network interface eth2 to enp131s0f0Mar  7 03:05:25 localhost systemd-udevd[415]: renamed network interface eth4 to enp134s0f0Mar  7 03:05:25 localhost systemd-udevd[416]: renamed network interface eth5 to enp134s0f1Mar  7 03:05:30 localhost systemd: Starting Import network configuration from initramfs...Mar  7 03:05:30 localhost systemd: Started Import network configuration from initramfs.Mar  7 03:05:40 localhost systemd: Starting Rollback uncommitted netcf network config change transactions...Mar  7 03:05:40 localhost systemd: Started Rollback uncommitted netcf network config change transactions.Mar  7 03:05:43 localhost systemd: Starting LSB: Bring up/down networking...Mar  7 03:05:45 localhost network: Bringing up loopback interface:  [  OK  ]Mar  7 03:05:45 localhost network: Bringing up interface br0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device br0 does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost /etc/sysconfig/network-scripts/ifup-eth: Device br0 does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost network: [FAILED]Mar  7 03:05:45 localhost network: Bringing up interface enp1s0f0:  [  OK  ]Mar  7 03:05:45 localhost network: Bringing up interface enp8s0f0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost /etc/sysconfig/network-scripts/ifup-eth: Device  does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost network: [FAILED]Mar  7 03:05:45 localhost network: Bringing up interface enp8s0f1:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost /etc/sysconfig/network-scripts/ifup-eth: Device  does not seem to be present, delaying initialization.Mar  7 03:05:45 localhost network: [FAILED]Mar  7 03:05:45 localhost systemd: network.service: control process exited, code=exited status=1Mar  7 03:05:45 localhost systemd: Failed to start LSB: Bring up/down networking.Mar  7 03:05:45 localhost systemd: Unit network.service entered failed state.Mar  7 03:05:48 localhost xinetd[1863]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.

image.png



ip addr查看这俩网卡的MAC:


[root@localhost network-scripts]# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN     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 forever2: enp1s0f0: mtu 1500 qdisc mq master br0 state UP qlen 1000    link/ether 00:25:90:64:a9:30 brd ff:ff:ff:ff:ff:ff    inet6 fe80::225:90ff:fe64:a930/64 scope link        valid_lft forever preferred_lft forever3: enp1s0f1: mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:25:90:64:a9:31 brd ff:ff:ff:ff:ff:ff4: enp8s0f0: mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:bd:05:4e:cc brd ff:ff:ff:ff:ff:ff5: enp8s0f1: mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:bd:05:4e:cd brd ff:ff:ff:ff:ff:ff6: enp8s0f2: mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:bd:05:4e:ce brd ff:ff:ff:ff:ff:ff7: enp8s0f3: mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:bd:05:4e:cf brd ff:ff:ff:ff:ff:ff



然后把这俩网卡的mac写到配置文件里:


/etc/sysconfig/network-scripts/ifcfg-enp8s0f0
/etc/sysconfig/network-scripts/ifcfg-enp8s0f1


添加:


HWADDR=00:0c:bd:05:4e:cc


然后重新启动network,就OK啦!


image.png


很久没更新了,其实问题不一定是MAC的问题,也有其他的可能性。下面是另一种情况:


虚拟机里边的CentOS7重启之后无法联网了,重启network发现报错。



百度了一圈,都是叫修改mac地址的说法,但是改了之后并没有什么用,最后谷歌解决了。



解决方式:禁用NetworkManager


1. systemctl stop NetworkManager


2. systemctl disable NetworkManager


然后重启网络服务,能正常联网了!


目录
相关文章
|
6月前
|
安全 Linux Shell
使用SCP命令在CentOS 7上向目标服务器传输文件
以上步骤是在CentOS 7系统上使用SCP命令进行文件传输的基础,操作简洁,易于理解。务必在执行命令前确认好各项参数,尤其是目录路径和文件名,以避免不必要的传输错误。
622 17
|
8月前
|
Ubuntu 安全 Linux
CentOS与Ubuntu中防火墙配置命令集汇
有了这些,你就能遨游在 CentOS 和 Ubuntu 的海洋中,频繁地改变你的防火墙设置,快速地应对各种安全威胁,同时也能保证你的系统可以正常工作。出发吧,勇敢的编程者,随着这些命令集的涌动,扬帆起航,走向安全的网络世界!
265 5
|
11月前
|
缓存 Ubuntu Linux
Linux中yum、rpm、apt-get、wget的区别,yum、rpm、apt-get常用命令,CentOS、Ubuntu中安装wget
通过本文,我们详细了解了 `yum`、`rpm`、`apt-get`和 `wget`的区别、常用命令以及在CentOS和Ubuntu中安装 `wget`的方法。`yum`和 `apt-get`是高层次的包管理器,分别用于RPM系和Debian系发行版,能够自动解决依赖问题;而 `rpm`是低层次的包管理工具,适合处理单个包;`wget`则是一个功能强大的下载工具,适用于各种下载任务。在实际使用中,根据系统类型和任务需求选择合适的工具,可以大大提高工作效率和系统管理的便利性。
1249 25
|
12月前
|
Ubuntu NoSQL Linux
《docker基础篇:3.Docker常用命令》包括帮助启动类命令、镜像命令、有镜像才能创建容器,这是根本前提(下载一个CentOS或者ubuntu镜像演示)、容器命令、小总结
《docker基础篇:3.Docker常用命令》包括帮助启动类命令、镜像命令、有镜像才能创建容器,这是根本前提(下载一个CentOS或者ubuntu镜像演示)、容器命令、小总结
604 6
《docker基础篇:3.Docker常用命令》包括帮助启动类命令、镜像命令、有镜像才能创建容器,这是根本前提(下载一个CentOS或者ubuntu镜像演示)、容器命令、小总结
|
Web App开发 网络协议 Linux
linux命令总结(centos):shell常用命令汇总,平时用不到,用到就懵逼忘了,于是专门写了这篇论文,【便持续更新】
这篇文章是关于Linux命令的总结,涵盖了从基础操作到网络配置等多个方面的命令及其使用方法。
404 1
linux命令总结(centos):shell常用命令汇总,平时用不到,用到就懵逼忘了,于是专门写了这篇论文,【便持续更新】
|
安全 Linux 网络安全
centos7中firewall防火墙的常用命令总结
以上命令集覆盖了 `firewalld`的基本操作,是维护CentOS 7系统安全不可或缺的工具。对于更高级的配置需求或遇到特定问题
296 3
|
网络协议 Linux Shell
CentOS7系统命令学习笔记(一)
CentOS7系统命令学习笔记(一)
336 12
|
Linux
CentOS7系统命令学习笔记(二)
CentOS7系统命令学习笔记(二)
306 10
|
Linux Shell API
CentOS7系统命令学习笔记(三)
CentOS7系统命令学习笔记(三)
217 8
|
Linux 编译器 C语言
./build.sh:行1: g++: 未找到命令的错误问题在centos操作系统下面如何解决
通过上述步骤,您应该能够有效地解决CentOS系统中 `g++: 未找到命令`的错误。确保软件开发环境配置得当,对于顺利执行编译脚本和日常开发工作至关重要。如果问题依然存在,考虑检查脚本内的命令路径引用是否正确,或进一步排查系统配置问题。
607 0