Help Center/
CodeArts Deploy/
FAQs/
Command Execution for Deployment Actions/
Running Shell Commands
Updated on 2025-07-04 GMT+08:00
Running Shell Commands
- A Message Indicating an Operation Failure Is Displayed
- 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
- What Should I Do If the Application Deployment Is Interrupted?
- What Should I Do If the Permission Is Insufficient?
- What Should I Do If Parameters Contain Backslashes (\)?
- What Should I Do If the Log Message "No Host in the Environment" Is Displayed?
- What Should I Do If the Log Message "Environment Cannot Be Found" Is Displayed?
- What Should I Do If an Error Is Reported When the sudo Permission Is Used?
- What Should I Do If the Deployment Process Is Intercepted by Third-Party Antivirus Software?
- What Should I Do If the Log Indicating an Invalid Path Is Displayed?
- What Should If Do If a Network Error Occurs During Software Installation on CentOS?
- What Should If Do If a Network Error Occurs During Software Installation on Ubuntu OS?
- What Should I Do If a Windows Path Is Not Allowed on a Linux Host?
- Other FAQs
Parent topic: Command Execution for Deployment Actions
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