Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
SecMaster
SecMaster
- What's New
- Function Overview
- Service Overview
-
Billing
- Billing Overview
- Billing Modes
- Billing Items
- Billing Examples
- Changing the Billing Mode
- Renewing Your Subscription
- Bills
- About Arrears
- Billing Termination
- Cost Management
-
Billing FAQs
- How Is SecMaster Billed?
- Can I Use SecMaster for Free?
- How Do I Change or Disable Auto Renewal for SecMaster?
- Will SecMaster Be Billed After It Expires?
- How Do I Renew SecMaster?
- Where Can I Unsubscribe from SecMaster?
- Where Can I View the Remaining Quotas of Security Data Collection and Security Data Packages?
- Can I Change the Billing Mode for SecMaster?
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Checking Security Overview
- Workspaces
- Viewing Purchased Resources
-
Security Governance
- Security Governance Overview
- Security Compliance Pack Description
- Authorizing SecMaster to Access Cloud Service Resources
- Subscribing to or Unsubscribing from a Compliance Pack
- Starting a Self-Assessment
- Viewing Security Compliance Overview
- Viewing Evaluation Results
- Viewing Policy Scanning Results
- Downloading a Compliance Report
- Security Situation
- Resource Manager
- Risk Prevention
- Threats
- Security Orchestration
-
Playbook Overview
- Ransomware Incident Response Solution
- Attack Link Analysis Alert Notification
- HSS Isolation and Killing of Malware
- Automatic Renaming of Alert Names
- Auto High-Risk Vulnerability Notification
- Automatic Notification of High-Risk Alerts
- Auto Blocking for High-risk Alerts
- Real-time Notification of Critical Organization and Management Operations
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Data Collection Process
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Verifying Log Collection
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- Key Operations Recorded by CTS
-
Best Practices
-
Log Access and Transfer Operation Guide
- Solution Overview
- Resource Planning
- Process Flow
-
Procedure
- (Optional) Step 1: Buy an ECS
- (Optional) Step 2: Buy a Data Disk
- (Optional) Step 3: Attach a Data Disk
- Step 4: Create a Non-administrator IAM User
- Step 5: Configure Network Connection
- Step 6: Install the Component Controller (isap-agent)
- Step 7: Install the Log Collection Component (Logstash)
- (Optional) Step 8: Creating a Log Storage Pipeline
- Step 9: Configure a Connector
- (Optional) Step 10: Configure a Log Parser
- Step 11: Configure a Log Collection Channel
- Step 12: Verify Log Access and Transfer
- Credential Leakage Response Solution
-
Log Access and Transfer Operation Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Alert Management
- Incident Management
- Indicator Management
- Playbook Management
- Alert Rule Management
- Playbook Version Management
- Playbook Rule Management
- Playbook Instance Management
- Playbook Approval Management
- Playbook Action Management
- Incident Relationship Management
- Data Class Management
- Workflow Management
- Data Space Management
- Pipelines
- Workspace Management
- Metering and Billing
- Metric Query
- Baseline Inspection
- Appendix
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
-
Security Governance
- Security Governance Overview
- Security Compliance Pack Description
- Authorizing SecMaster to Access Cloud Service Resources
- Subscribing to or Unsubscribing from a Compliance Pack
- Starting a Self-Assessment
- Viewing Security Compliance Overview
- Viewing Evaluation Results
- Viewing Policy Scanning Results
- Downloading a Compliance Report
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- Security Orchestration
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- FAQs
- Change History
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Authorizing SecMaster
- Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
-
Risk Prevention
-
Baseline Inspection
- Baseline Inspection Overview
- Creating a Custom Check Plan
- Starting an Immediate Baseline Check
- Viewing Check Results
- Handling Check Results
- Viewing Compliance Packs
- Creating a Custom Compliance Pack
- Importing and Exporting a Compliance Pack
- Viewing Check Items
- Creating a Custom Check Item
- Importing and Exporting Check Items
- Vulnerability Management
- Policy Management
-
Baseline Inspection
-
Threat Operations
- Incident Management
- Alert Management
- Indicator Management
- Intelligent Modeling
- Security Analysis
- Data Delivery
-
Security Orchestration
- Security Orchestration Overview
- Built-in Playbooks
- Security Orchestration Process
- (Optional) Configuring and Enabling a Workflow
- Configuring and Enabling a Playbook
- Operation Object Management
- Playbook Orchestration Management
- Layout Management
- Plug-in Management
- Settings
-
FAQs
-
Product Consulting
- Why Is There No Attack Data or Only A Small Amount of Attack Data?
- Where Does SecMaster Obtain Its Data From?
- What Are the Dependencies and Differences Between SecMaster and Other Security Services?
- What Are the Differences Between SecMaster and HSS?
- How Do I Update My Security Score?
- How Do I Handle a Brute-force Attack?
- Issues About Data Synchronization and Data Consistency
- About Data Collection Faults
-
Product Consulting
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
On this page
- Possible Cause 1: The Network Between the ECS Where You Want to Install isap-agent and the OBS Bucket Storing the Agent Is Disconnected
- Possible Cause 2: Insufficient Disk Space on the ECS
- Possible Cause 4: Failed to Verify the Workspace ID
- Possible Cause 5: isap-agent Installed Repeatedly When isap-agent Has Already Been Installed
- Possible Cause 6: Disconnected Network Between ECS and DNS
- Possible Cause 7: The Workspace Does Not Exist or the Account Lacks Permission.
- Possible Cause 8: Disk Not Partitioned
Show all
Help Center/
SecMaster/
User Guide (ME-Abu Dhabi Region)/
FAQs/
Data Collection/
Why Did the Component Controller Fail to Be Installed?
Copied.
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.
- Log in to the OBS management console.
- In the navigation pane on the left, choose Buckets. On the displayed page, click the name of the target bucket.
- On the displayed details page, download the installation script and installation package.
- Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
- 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
CAUTION:
- (Optional) Method 1: Deregister the node on the management console.
- Log in to the SecMaster management 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 Nodes tab, locate the row that contains the target node and click Deregister in the Operation column.
- In the displayed dialog box, click OK.
- (Optional) Method 2: Run a script command to uninstall component controller isap-agent.
- Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
- Run the sh /opt/cloud/agent_controller_euler.sh uninstall command to uninstall the component controller.
- Check whether the uninstallation is complete.
- Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
- (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
- (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
CAUTION:
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.
Parent topic: Data Collection
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
