Centos7 failed to start Network (service network restart) error resolution (GO)

Source: Internet
Author: User

CENTOS7 Unable to start the Network (Service network restart) Error resolution:
(The following methods are online copy, but also thank Yumbo Master sharing)

Systemctl status Network.service The following error occurred
Workaround for "Rtnetlink answers file exists"

The first kind: and NetworkManager service conflict, this good solution, directly shut down the Networkmanger service is good, services

NetworkManager stop, and disable boot chkconfig NetworkManager off. After that, it's good to restart. (I use the first kind of success)

The second kind: and the configuration file MAC address does not match, this solves, directly modifies the/etc/udev/rules.d/70-persistent-net.rules file the Mac

The address is as good as the/etc/sysconfig/network-scripts/ifcfg-eth0.

(You can try this if you can't do two kinds of things.)
IP addr Flush Dev enoxxxxx
(Copy address: http://www.2cto.com/os/201411/350848.html)


Three ways to solve Failed to start lsb:bring Up/down networking problem


《—》
1. The following error occurred while executing service network restart
Restarting network (via Systemctl): Job for Network.service failed. See ' Systemctl status Network.service '
and ' Journalctl-xn ' for details.

2, according to the above prompts, perform "Systemctl status Network.service" output the following similar information:

[Email protected] ~]# systemctl status Network.service
Network.service-lsb:bring Up/down Networking
Loaded:loaded (/etc/rc.d/init.d/network)
Active:failed (Result:exit-code) since three 2014-11-05 15:30:10 CST; 1min 5s ago
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain network[2920]: Rtnetlink answers:file exists
November 15:30:10 localhost.localdomain systemd[1]: Network.service:control process exited, code=exited
Status=1
November 15:30:10 localhost.localdomain systemd[1]: Failed to start lsb:bring up/down networking.
November 15:30:10 localhost.localdomain systemd[1]: Unit Network.service entered failed state.

3, the solution (because there is no 70-persistent-net.rules this file in Centos7, the virtual machine (VMware) will need to modify the MAC address)
is to modify the MAC address.

4, how to view the MAC address of the virtual machine Centos7 copied, need to perform "IP addr", output the following similar information:
[[Email protected] ~]# IP addr

1:lo:

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:eno16777736:
Link/ether00:0f:19:10:12:f1BRD FF:FF:FF:FF:FF:FF
inet 192.168.38.135/24 BRD 192.168.38.255 scope Global Dynamic eno16777736
Valid_lft 1681sec preferred_lft 1681sec
Inet6 FE80::20C:11AA:AE11:4FE4/64 Scope link
Valid_lft Forever Preferred_lft Forever

Notice the bold and red words above, this is the new MAC address.
The next step is to modify the Ifcfg-xxx file, only modify the hwaddr on it. The next execution of the service network restart is normal.

Two

If it fails to start, see if you have the following error message

Nov 22:09:07 Hdcoe02 network[597]: Bringing up loopback interface:could not load file
'/etc/sysconfig/network-scripts/ifcfg-lo '
Nov 22:09:07 hdcoe02 network[597]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo '
Nov 22:09:08 hdcoe02 network[597]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo '
Nov 22:09:08 hdcoe02 network[597]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo ' Nov 23
22:09:08 HDCOE02 network[597]: [OK]
Nov 22:09:08 Hdcoe02 network[597]: Bringing up interface Enp0s25:Error:Connection activation failed:
Connection ' ENP0S25 ' is not available on the device ENP0S25 at this time.

Set boot start a service named Networkmanager-wait-online, the command is:
Systemctl Enable Networkmanager-wait-online.service

Three

I am also the above method has been the test has been unsuccessful, and finally found because the VMware virtual machine inside the system in the upper right corner of the connection is not connected,
Although the error is the same, I finally in the virtual machine settings inside the original network adapter deleted, re-built a new network adapter, this time to go in, show the connection
Success, and then use the above method, problem solving.
(Copy address: http://blog.csdn.net/qq_21398167/article/details/46694179)

Centos7 failed to start Network (service network restart) error resolution (GO)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.