problem overview

about this problem, the blogger encountered in the process of virtual machine migration. After the migration, the network needs to be reallocated. After the configuration is completed, when the network service is restarted, the error is reported: “Job for network. Service failed because the control process exited with error code. See “systemctl status network. Service” and “journalctl-xe” for details

as follows:

to check the network status, enter the command “systemctl status net.service”, as shown in the figure below:

network service failed to start!!

solution

check for a while, finally found is an extra network configuration file, as shown in the figure below:

the reason is caused by the old file web services launch failure, delete the old file, found again to restart the network service, altogether OK
1. Delete old file and enter the command “rm-rf ifcfg-ens33.old”;

2. Restart the network service, enter the command “systemctl restart net.service”;

3. To check whether the network service has been started successfully, enter the command “systemctl status net.service”, as shown in the figure below:

supplement

on December 16, 2019

the usual virtual machine network mode is NAT bridging mode, so the virtual machine related services need to be started, as shown in the figure below:

the first one is automatically assigned IP address, the second one is network bridging NAT, these two must be started, otherwise the virtual machine network will not be able to use.

well, the solution for Job for network. Service failed because the control process exited with error code. See “systemc “has been written here.
.
.

The