Diese Seite ist in Ihrer lokalen Sprache noch nicht verfügbar. Wir arbeiten daran, weitere Sprachversionen hinzuzufügen. Vielen Dank für Ihre Unterstützung.
CodeArts Deploy
CodeArts Deploy
- Service Overview
- Getting Started
-
User Guide
- Overview
- Managing Basic Resources
-
Managing Applications
- Creating an Application
- Editing an Application
- Deploying an Application
- Viewing an Application
- Managing Groups
- Following/Cloning/Deleting Applications
-
Deployment Actions
- Health Test via URLs
- Selecting a Deployment Source
- Stopping a Service
- Copying a File
- Deleting a File
- Decompressing a File
- Modifying a Configuration File
- Starting or Stopping Tomcat
- Starting or Stopping Spring Boot
- Starting or Stopping Nginx
- Starting or Stopping IIS
- Starting or Stopping Node.js
- Starting or Stopping the Go service
- Running Shell Commands
- Running Shell Scripts
- Running PowerShell Commands
- Running PowerShell Scripts
- Running Docker Commands
- Wait
- Deploying on Kubernetes
- Deploying an Application in Kubernetes (CCE Cluster) Using Manifest
- Deploying an Application in Kubernetes (CCE Cluster) Quickly
- Deploying an Application with a Custom Kubernetes Cluster
- Kubernetes Nginx-Ingress Grayscale Deployment (CCE Cluster)
- Deploying with Helm3
- Ansible
- Creating IIS Site
- Installing IIS
- Installing JDK
- Installing Tomcat
- Installing Nginx
- Installing Go
- Installing PHP
- Installing Node.js
- Installing Python
- Installing/Uninstalling Docker
- Istio Gray Release
- Deploying to FunctionGraph
- FunctionGraph Grayscale Release
-
Managing Orchestration Templates
- Background
-
System Templates
- Deploying to FunctionGraph
- Deploying a Tomcat Application
- Deploying a Spring Boot Application
- Deploying a Docker Application (Linux)
- Deploying a Django Application
- Deploying a Node.js Application
- Deploying a General Application
- Deploying an Application in Kubernetes (CCE Cluster) Using Manifest
- Deploying an Application in Kubernetes (CCE Cluster) Quickly
- Deploying an Application with a Custom Kubernetes Cluster
- Deploying a Go Application
- Custom Templates
- Managing Parameters
- Managing Permissions
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- Host Cluster Management
- Host Management
-
Application Management
- Obtaining an Application List (Recommended)
- Creating an Application (Recommended)
- Deploying an Application
- Obtaining Application Details (Recommended)
- Deleting an Application (Recommended)
- Querying the Historical Deployment Records of a Specified Application in a Project by the Start Time and End Time
- Querying Execution Parameters of a Deployment Record
- Deployment Record Measurement
- Environment Management
- Application Examples
- Appendixes
-
FAQs
- Hosts
- Environment Management
- Permissions Related to CodeArts Deploy
-
Creating an Application
- Draft Applications Cannot Be Deployed
- Error Messages Displayed During Application Deployment
- How Do I Find the Cause of an Application Deployment Error in Logs?
- Error 403 Displayed During Application Deployment That Requires CCE Resources, Indicating Insufficient Permission
- How Do I Roll Back a Deployed Version?
- Why Do I Fail to Obtain an Endpoint?
- Application Deployment Timed Out
-
Custom Application Actions
-
Health Test via URLs
- Incorrect URL
- URL Does Not Exist
- Invalid URL
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Selecting Deployment Sources
- Software Package Not Found in CodeArts Artifact
- No Software Package Available for a Build Task
- URL Domain Name Resolution Failure
- File Download Times Out
- Inconsistent SHA256 Values in a File
- Inconsistent MD5 Values in a File
- Error "More than 100 build files"
- "HTTP Error 403" Is Displayed When the CodeArts Artifact Software Package Is Downloaded
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Stopping a Service
- Incorrect Port Number
- Action Stop Service Deployed Successfully, But the Service Is Still in Started State
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Copying a File
- File to Be Copied Does Not Exist
- Invalid File Path
- File or File Path Does Not Exist
- Action Copy Files Deployed Successfully, But the Expected Result Is Not Achieved
- Insufficient Permissions
- Log Contains "copy File Failed" When Copying Files Between Linux Environment
- Log Contains "Windows does not support copying files between hosts" When Copying Files Between Windows Environment
- Log Contains "Hosts using secret key credit do not support copying files between" When Copying Files Between Environment
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Deleting a File
- Cannot Delete Files on a Linux Host
- File Path Does Not Exist on a Windows Host
- Incorrect File Path on a Windows Host
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Decompressing a File
- File to Be Decompressed Does Not Exist
- Backslashes (\) Are Used as Path Separators in the Native Command Compress-Archive
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Modifying a Configuration File
- File Path Does Not Exist
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Tomcat
- Invalid Tomcat Path
- Stopping Failed
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting/Stopping Go Service
- The Go Service Path Is Incorrect
- Startup Failed
- Environment Variables Are Not Configured
- Deployment Is Successful, But the Service Is Not Started
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Spring Boot
- Invalid Spring Boot Path
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Spring Boot Can Still Be Detected After Being Stopped (on Windows)
- Instruction
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Nginx
- Nginx Gets Restarted Repeatedly
- Invalid Windows Host Path
- Deploying the Command for Stopping Nginx When Nginx Is Not Started
- Incorrect Format of the Nginx Configuration File
- Configuration File Backup Path Does Not Exist
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Starting or Stopping IIS
-
Starting or Stopping Node.js
- Node.js Fails to Be Started or Stopped on a Linux Host
- Node.js Fails to Be Started or Stopped on a Windows Host
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Running Shell Commands
- A Message Indicating an Operation Failure Is Displayed During Action Run Shell Commands Deployment
- Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed
- Unidentified Shell Commands Are Used
- Shell Command References a File or Folder That Does Not Exist
- How Does a Shell Command Reference Parameters?
- Deployment of the Action Run Shell Commands Times Out
- Interactive Shell Commands Are Used
- Shell Command Deployment Times Out After the su Command Is Executed to Switch the User
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
- Other FAQs
-
Running Shell Scripts
- Running Shell Scripts Failed
- Deployment Is Successful But Does Not Achieve the Expected Result
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Running PowerShell Commands
- Deployment of the Action Run PowerShell Commands Times Out
- Unidentified PowerShell Commands Are Used
- PowerShell Command References a File or Folder That Does Not Exist
- How Does a PowerShell Command Reference Parameters?
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
-
Running PowerShell Scripts
- Running PowerShell Scripts Failed
- Deployment Is Successful But Does Not Achieve the Expected Result
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
-
Running Docker Commands
- Docker Not Installed
- Docker Command Parameter Error
- No Deployment Permissions
- Image Does Not Exist
- login Command Execution Failed
- build Command Execution Failed
- tag Command Execution Failed
- push Command Execution Failed
- run Command Execution Failed
- start, restart, stop, or rm Command Execution Failed
- rmi Command Execution Failed
- pull Command Execution Failed
- rm Command Execution Failed
- Connection Timed Out
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Pending Execution
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
FAQs About Kubernetes Deployment Tasks
- Parameter Referenced by {{}} in the YML File Is Not Defined in the Application
- Target File Does Not Exist in CodeArts Artifact
- Path of the YML File in CodeArts Artifact Is Incorrect
- kubeconfig File Is Incorrectly Configured
- kubectl Command Fails to Be Deployed
- Failed to Deploy Applications on Kubernetes
- Log Contains "Too many files to unzip" When CodeArts Repo Is Selected as the YML File Source During Kubernetes Deployment
- Error Message "File is too large" Displayed During YML File Source Selection for Kubernetes Deployment
-
Ansible
- Invalid Entry File Path
- Entry File Not Found
- Copy Module Error
- JSON Parameter Parsing Error
- Service Module in Playbook Scripts Fails to Start or Stop Services
- Ansible Application Deployment Fails
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Creating an IIS Site
- Incorrect Port Number
- Physical Path of an Application Does Not Exist
- IIS Not Installed on the Host
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- How Do I Check the IIS Function on the Local Host?
- Installing IIS
-
Installing JDK
- A JDK of the Same Version Already Exists on the Target Host
- Java Not Installed on the Target Host
- JDK Decompression Failed
- Cannot Install OpenJDK 8 on Ubuntu 14 or Earlier Versions
- OpenJDK Does Not Support Arm
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Tomcat
- Deployment Failed
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Nginx
- No sudo Permissions
- No Permission to Access the Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Go
- Invalid Installation Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing PHP
- Error Returned When Installing PHP as a Common User
- Some Dependency Packages Do Not Exist in the CentOS Yum Repository
- Download Fails Due to Network Disconnection from the CentOS Yum Source
- Download Fails Because Some Dependency Packages Are Missing for apt-get in Ubuntu
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Node.js
- Cannot Decompress Node Packages
- Installation Path Fails to Be Created
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Python
- No sudo Permissions
- No Permission to Access the Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing/Uninstalling Docker
- Error Returned During the Deployment of the Action for Installing or Uninstalling Docker as a Common User
- Error Returned Even Though the Action for Installing or Uninstalling Docker Is Successfully Deployed
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment.
- Environment Does Not Exist.
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Health Test via URLs
- Application Deployment
-
Common FAQs
- Failure in Querying Deployment Status
- Application Does Not Exist
- Can I Use a Host to Deploy Multiple Projects?
- Do I Need to Install a Running Environment (Tomcat, Python, etc.) on the Target Host Before Deploying an Application?
- CodeArts Deploy Fails to Download Files from CodeArts Artifact Due to a Spelling Error
- Application Deployment Fails, with the Message "AnsibleUndefinedVariable: 'xxxx' is undefined" Displayed
- Application Deployment Succeeds But the Application Verification URL Cannot Be Accessed
- What Can I Do If Application Deployment Fails Due to a DNS Resolution Error?
- Draft Applications Cannot Be Deployed
- JDK Has Been Installed and Environment Variables Have Been Configured, But Application Deployment Fails with the Error Message "please configure JDK environment variables" Displayed
- Insufficient Permissions
- Invalid Path
- No Host Exists in the Environment.
- Error Occurs During Application Deployment with the sudo Privileges
- File or File Path Does Not Exist
- Insufficient Permissions
- File Path Does Not Exist
On this page
Show all
Help Center/
CodeArts Deploy/
FAQs/
Custom Application Actions/
Installing Node.js/
Installation Path Fails to Be Created
Installation Path Fails to Be Created
Updated on 2023-11-28 GMT+08:00
Symptoms
The following log information is displayed.
Figure 1 Log information
Cause Analysis
Ansible is used when installing Node.js. When entering a Windows path, use forward slashes (/) instead of backslashes (\).
Solution
Check whether the installation path is correct. If the installation path is a Windows path, ensure that the path contains forward slashes (/).
Parent topic: Installing Node.js
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
