Service network restart failed.
Cause of error: Job for Network.service failed because-control process exited with error code. "Systemctl status Network.service" and "Journalctl-xe" for details.
Check: Systemctl status Network.service
Output:
[Root@localhost network-scripts]# 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 three 2017-02-15 17:23:49 CST; 10s ago
Docs:man:systemd-sysv-generator (8)
process:4556 execstop=/etc/rc.d/init.d/network Stop (code=exited, status=0/success)
process:4728 execstart=/etc/rc.d/init.d/network Start (code=exited, Status=1/failure)
February 17:23:48 Localhost.localdomain systemd[1]: Starting lsb:bring up/down netw ....
February 17:23:48 Localhost.localdomain network[4728]: Opening loopback interface: [OK]
February 17:23:49 Localhost.localdomain network[4728]: Opening interface ENS33: Error: Excitation ... on.
February 17:23:49 Localhost.localdomain network[4728]: [Failed]
February 17:23:49 localhost.localdomain systemd[1]: Network.service:control process ... 1
February 17:23:49 localhost.localdomain systemd[1]: Failed to start lsb:bring up/do ....
February 17:23:49 localhost.localdomain systemd[1]: unit Network.service entered FAI ....
February 17:23:49 localhost.localdomain systemd[1]: Network.service failed.
Hint:some lines were ellipsized, use-l.
Trampled on countless pits, so it is:
Input: Ifconfig
Get ether,
Find the ifcfg-ens123 in the/etc/sysconfig/network-scripts (the following number is different from the computer), the ether and hwaddr configuration,
Again service network restart
If the clone will cause a MAC address conflict, see here. http://blog.csdn.net/ymd8005/article/details/54948558