Why Did the Component Controller Fail to Be Installed?

A component controller (isap-agent) needs to be installed on ECSs for security data collection. If the installation fails, you can fix the fault by following the instructions provided in this section.

For details about common commands used during troubleshooting, see Which Commands Are Commonly Used for the Component Controller?

Possible Cause 1: The Network Between the ECS Where You Want to Install isap-agent and the OBS Bucket Storing the Agent Is Disconnected

Figure 1 Disconnected network between the target ECS and OBS bucket

Solution

(Optional) Method 1: Connect the ECS to OBS.
(Optional) Method 2: Manually download the installation script and installation package to the local PC, and upload the installation package to the /opt/cloud directory on the server.
1. Log in to the OBS management console.
2. In the navigation pane on the left, choose Buckets. On the displayed page, click the name of the target bucket.
3. On the displayed details page, download the installation script and installation package.
4. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
5. Upload the installation package to the /opt/cloud directory on the server.

Possible Cause 2: Insufficient Disk Space on the ECS

Figure 2 Insufficient disk space

Solution

Clear the disk to reserve sufficient space.

Possible Cause 4: Failed to Verify the Workspace ID

If the information shown in the following figure is displayed, the workspace ID verification failed.

Figure 3 Workspace ID verification failed

Solution

Log in to the SecMaster console.
In the navigation pane on the left, choose Workspaces. In the workspace list, click the name of the target workspace.
In the navigation pane on the left, choose Settings > Components. On the displayed page, click the target node.
Check workspace ID and project ID in the command output.
Figure 4 Parameters on the console
Check whether the workspace ID and project ID in the command are the same as those in the file in 4.
Figure 5 Parameter information in the command
Use a valid workspace ID and project ID to run the command again.

Possible Cause 5: isap-agent Installed Repeatedly When isap-agent Has Already Been Installed

If the information shown in the following figure is displayed, the Agent has been installed.

Figure 6 Agent already installed

Solution

(Optional) Method 1: Deregister the node on the management console.
1. Log in to the SecMaster management console.
2. In the navigation pane on the left, choose Workspaces. In the workspace list, click the name of the target workspace.
3. In the navigation pane on the left, choose Settings > Components. On the displayed Nodes tab, locate the row that contains the target node and click Deregister in the Operation column.
4. In the displayed dialog box, click OK.
(Optional) Method 2: Run a script command to uninstall component controller isap-agent.
1. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
2. Run the sh /opt/cloud/agent_controller_euler.sh uninstall command to uninstall the component controller.
Check whether the uninstallation is complete.
1. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
2. (Optional) Method 1: Run the ls -a /opt/cloud/ command to view the files in the /opt/cloud directory. If the information shown in the following figure is displayed (including only the script file), the uninstallation is complete.
  Figure 7 Script file
3. (Optional) Method 2: Run the salt-minion --version command. If the following information is displayed, the uninstallation is complete.
  Figure 8 Checking isap-agent details

It takes some time to deregister a node. Do not install the Agent until you confirm that the node has been deregistered.

Possible Cause 6: Disconnected Network Between ECS and DNS

During the isap-agent installation, the message "Could not resolve host:*******" is displayed.

Figure 9 Error message indicating that the network between the ECS and DNS is disconnected

The installation failed because the network between the ECS and DNS was disconnected.

Figure 10 Disconnected network between the target ECS and DNS

Solution

In the VPC the ECS belongs to, enter the correct DNS resolution address. For details, see "How Do I Change the DNS Server Address of an ECS?" in the Virtual Private Cloud User Guide.

Possible Cause 7: The Workspace Does Not Exist or the Account Lacks Permission.

During the isap-agent installation, the following information is displayed:

install isap-agent failure

Tip: Please check the workspace status and reinstall

Figure 11 Error message indicating that the workspace does not exist or the account lacks permission

Solution

Check whether the current workspace exists.
Check whether the SecMaster machine-machine account that has the minimum permission is correctly configured.

Possible Cause 8: Disk Not Partitioned

During the isap-agent installation, the message "The directory space of /opt is too small" is displayed.

Figure 12 Disk not partitioned

Solution

Run the following command on the installation page:
sh /opt/cloud/isap-agent/action/agent_controller_linux.sh partition

For details, see Partitioning a Disk.
Reinstall isap-agent.
For details, see Installing the Component Controller.