What Do I Do If the Agent Fails to Be Installed on a Server?
If the agent fails to be installed, rectify the fault by following the instructions provided in this section.
Failed to Install the Agent on the HSS Console
If the agent fails to be installed on the console, rectify the fault based on the information displayed on the HSS management console and Table 1.
| Console Message | Suggestion |
|---|---|
| Network disconnected and access timed out. Check your network configurations. |
|
| Authentication failed due to incorrect password. Check the password. | The password is incorrect. Check the password information you entered. |
| There are no private keys managed by DEW. Please check DEW. | Check and restore your DEW key pair to the Managed state. |
| Metadata check failed. Check the metadata information. | Failed to obtain the metadata. For details, see Why Can't My Linux ECS Obtain Metadata? |
| Failed to install Expect. Check the Expect installation information. | Check whether the network fluctuates. After the network recovers, install the agent again. If the network is normal but the installation still fails, choose Service Tickets > Create Service Ticket in the upper right corner of the Huawei Cloud management console to contact technical support. |
| Failed to connect to VPC. Acquire VPCOperatePolicy permissions and try again. | HSS does not have the VPCOperatePolicy permission so it cannot communicate with each other between VPCs. You are advised to perform the following operations to grant the permission:
For details about the VPCOperatePolicy permission, see Authorization. |
| Cannot find the key pair of this server in DEW. Check whether the key pair exists. | Check whether your DEW key pair exists. |
| Failed to connect to VPCEP. Ensure you have VPCOperatePolicy permissions and check available IP addresses. | HSS cannot create a VPC endpoint (used for communication between the agent and the HSS server) because the VPCEPOperatePolicy permission is not granted to HSS. As a result, the agent fails to be installed. You are advised to perform the following operations to grant the permission:
For details about the VPCEPOperatePolicy permission, see Authorization. |
| Failed to log in using the key. Check whether the key is correct. | The key is incorrect. Check the key information you entered. |
| Insufficient permissions to run the installation command. | Possible cause: The script cannot be executed in the /tmp directory, or bash does not have the execution permission. Suggestion:
|
| Failed to download the installation file. Log in to the server, run the installation command, and check whether the master can be accessed. If the access fails, check security group and DNS configurations. | This error occurs only on Linux servers. You are advised to perform the following operations to check the security group and DNS configurations.
|
| Insufficient disk space. | Check the following directories to ensure that the disk capacity is sufficient:
|
| No key pairs returned from DEW. Verify permissions first. | Check and ensure your key pair is managed by DEW. If the key pair is already managed by DEW, but HSS still displays a message indicating that the managed private key is not found when you install the agent, the possible cause is that your current account is an IAM member account or delegated account and does not have the permissions for KPS in DEW. You can go to the IAM console and use any of the following methods to grant permissions:
If you do not want the agent installation account to have the permission to delete key pairs, you can create the following custom policy and grant the policy to the account. For details, see Creating a Custom Policy. Policy for allowing users to query and export key pairs: {
"Version": "1.1",
"Statement": [
{
"Action": [
"kps:domainKeypairs:exportpk",
"kps:domainKeypairs:list",
"kps:domainKeypairs:get"
],
"Effect": "Allow
}
] After creating a policy, grant permissions by referring to Authorization method 1. You only need to change DEW KeypairFullAccess in authorization method 1 to a custom policy. |
| Installation error. | Perform the following operations:
|
| Cannot connect to the target VPC due to NIC route conflicts. Install the agent using the CLI, or upgrade an agent in that VPC. | A route conflict occurs between the NIC of your server and the elastic NIC attached to the server where the agent is being installed. The VPC network cannot be connected. You are advised to install the agent using commands. For details, see Using the Commands or Script to Install the Agent on Huawei Cloud Servers (Current-account Installation). |
| There is no VM with an online agent in the VPC of this server. Install or upgrade the agent using commands in the VPC. |
|
| Installation failed | Install the agent again. If the installation fails again, Click Service Tickets > Create Service Ticket in the upper right corner of the management console to contact technical support. |
Failed to Install the Agent Using Commands
If you fail to install the agent using commands (that is, by logging in to the server and running commands), rectify the fault based on the command output.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot












