1. Error:
today, I turned on the virtual machine to start a big data cluster. Because I didn’t turn on the machine for some time, I found that I couldn’t connect to the Internet after turning on the machine. After ifconfig, I didn’t even have an IP address:

2. Solution:
there are many opinions on the Internet. Most of them are to reconfigure the static IP of VI/etc/sysconfig/network scripts/ifcfg-ens33. In fact, the network card does not work. Finally, only one method works:

3 directives:

3. Reason:
on CentOS system, there are two network management tools, NetworkManager and network. Both configurations can cause conflicts. Generally, we use network to configure static IP. It may be that the shutdown (for some reason) causes the automatic configuration of NetworkManager, resulting in a conflict, so it’s good to disable it.

Temporary shutdown
systemctl stop NetworkManager
permanent shutdown
systemctl disable NetworkManager
Restart
systemctl restart network

Similar Posts:

• [Solved] Failed to start LSB: Bring up/down networking.
• [Solved] CentOS 7: Restarting network (via systemctl): Job for network.service failed
• Failed to restart network.service: Unit network.service not found
• Job for network.service failed because the control process exited with error code [How to Solve]
• Centos7 Restart NIC error: Job for network.service failed because the control process exited with error code
• [Solved] Docker Container Start Error: iptables: No chain/target/match by that name
• [Solved] Centos7 linux ailed to stop iptables.service: Unit iptables.service not loaded.
• CentOS7 Failed to start LSB: Bring up/down [How to Solve]
• Pop up interface eth0: error: failed to activate connection: device not managed by NetworkManager or unavailable
• Linux: CentOS 7 executes service network restart error [Solved]