Disclaimer: this article may be contributed by the community or involve third-party product information. We recommend that you visit the community or the official website of third-party products for help and support. Third-party products will not be provided by Alibaba Cloud after-sales support. This document is for reference only. Alibaba Cloud makes no guarantee by express or any other means.
Problem description
If the corresponding network process does not exist in the instance and the network configuration is DHCP, the lease of IP addresses cannot be renewed after the lease expires. Then the instance connection fails.
Solution
Alibaba Cloud reminds you that:
- Before you perform operations that may cause risks, such as modifying instance configurations or data, we recommend that you check the disaster recovery and fault tolerance capabilities of the instances to ensure data security.
- You can modify the configurations and data of instances including but not limited to Elastic Compute Service (ECS) and Relational Database Service (RDS) instances. Before the modification, we recommend that you create snapshots or enable RDS log backup.
- If you have authorized or submitted sensitive information such as the logon account and password in the Alibaba Cloud Management Console, we recommend that you modify such information in a timely manner.
Troubleshooting
You can run the ps -ef | grep [$network process]
command to check whether the network process exists. If the corresponding network process does not exist, there are potential risks. The network processes corresponding to each system (using DHCP as the network configuration method) are as follows:
OS version |
Network processes |
CentOS 6/7;Debian 8/9/10;Ubuntu 14/16 |
/sbin/dhclient |
CentOS 8 |
/usr/sbin/NetworkManager |
Ubuntu 18/20;Alibaba Cloud Linux 2 |
/lib/systemd/systemd-networkd |
SLES 12/15;openSUSE 15 |
/usr/lib/wicked/bin/wickedd-dhcp4 |
Solution
If the system network service is abnormal or the network service process is absent, restart the network service to restore it. Different Linux have different network service names and different system versions have different network services. The name of the specified network service and the command for restarting the network service are as follows:
Warning: restarting the network service may cause the network to be interrupted for a short time.
OS |
Version |
Network service name |
Network Service Restart command |
CentOS |
6 |
network |
service network restart |
7 |
network |
systemctl restart network |
|
8 |
NetworkManager |
systemctl restart NetworkManager |
|
Debian |
8 |
networking |
systemctl restart networking |
9 |
networking |
systemctl restart networking |
|
10 |
networking |
systemctl restart networking |
|
Ubuntu |
14 |
networking |
service networking restart |
16 |
networking |
systemctl restart networking |
|
18 |
systemd-networkd |
systemctl restart systemd-networkd |
|
20 |
systemd-networkd |
systemctl restart systemd-networkd |
|
SLES |
15 |
wicked |
systemctl restart wicked |
12 |
wicked |
systemctl restart wicked |
|
openSUSE |
15 |
wicked |
systemctl restart wicked |
Alibaba Cloud Linux 2 |
2 |
systemd-networkd |
systemctl restart systemd-networkd |
Application scope
- Elastic Compute Service