/etc/init.d/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.
[fail]
Use the systemctl status network.service command to view the results as follows:
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed (Result: exit-code) since 三 2016-08-17 11:34:36 CST; 54s ago
Docs: man:systemd-sysv-generator(8)
Process: 3847 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn network[3847]: RTNETLINK answers: File exists
8月 17 11:34:36 python.cn systemd[1]: network.service: control process exited, code=exited status=1
8月 17 11:34:36 python.cn systemd[1]: Failed to start LSB: Bring up/down networking.
8月 17 11:34:36 python.cn systemd[1]: Unit network.service entered failed state.
8月 17 11:34:36 python.cn systemd[1]: network.service failed.
Looking at the system log, the error is as follows:
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python network: RTNETLINK answers: File exists
Aug 17 11:34:36 python systemd: network.service: control process exited, code=exited status=1
Aug 17 11:34:36 python systemd: Failed to start LSB: Bring up/down networking.
Aug 17 11:34:36 python systemd: Unit network.service entered failed state.
Aug 17 11:34:36 python systemd: network.service failed.
Aug 17 11:36:28 python systemd: Starting LSB: Bring up/down networking...
Aug 17 11:36:29 python network: Opening loopback interface: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Aug 17 11:36:29 python network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Aug 17 11:36:29 python network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Aug 17 11:36:29 python network: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Aug 17 11:36:29 python network: [OK]
Aug 17 11:36:29 python network: Opening interface eno16777736: Error: Failed to activate connection: No suitable device found for this connection.
After investigation, it is confirmed that the /etc/sysconfig/network-scripts/ifcfg-lo file exists. Where is the problem? No, I have to Baidu, the results from Baidu are basically the same.
Baidu answer:
The mac address is incorrect. Modify the mac address.
Maybe someone does have a mac problem, but somehow the mac address has changed unless you add a new network card or clone a virtual machine.
I'm really laughing, it's a big copy of Baidu articles all over the world. . . . . . . .
No way, Google it, I came across an article, to the effect that it has something to do with the management suite that comes with the system, NetworkManager, and it can be solved by turning it off.
try it:
systemctl stop NetworkManager
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.
Restart the network:
systemctl start network.service
ifconfig |grep eno
eno16777736: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.192 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::20c:29ff:fe3d:b305 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:3d:b3:05 txqueuelen 1000 (Ethernet)
RX packets 2 bytes 120 (120.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 3551 (3.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The network starts normally, and the access is normal.