Shulou(Shulou.com)06/03 Report--

What about the conflict between NetworkManager and network in linux? I believe that many inexperienced people are at a loss about this, so this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Problem phenomenon: the server network is down, the network is connected after service network restart restart, and then after a while (a few seconds), there are many dhcp processes in the system.

Then check the ifconfig no IP information

This phenomenon is caused by the failure to read the IP configuration to cause the system to start the dhcp allocation IP process

Then try to check / var/log/messages log and see a strange record

NetworkManager has attracted attention. Normally, there is no such service and this service is not configured.

OK after systemctl stop NetworkManagersystemctl disable NetworkManagerservice network restart starts network after trying to stop this service!

Problem resolution: the conflict between NetworkManager and network causes an exception, which is normal when NetworkManager is disabled

After reading this article, can you solve the conflict between NetworkManager and network independently? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel. Thank you for reading.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.