Help Center>
CodeArts Deploy>
FAQs>
Custom Application Actions>
Running Shell Commands>
Shell Command Deployment Times Out After the su Command Is Executed to Switch the User
Updated on 2023-11-28 GMT+08:00
Shell Command Deployment Times Out After the su Command Is Executed to Switch the User
Symptoms
When the shell command sudo su – test && echo hello is deployed, the progress is stuck in deploying state until timeout occurs.
Cause Analysis
After the su command is executed to switch to another user, the operation window of the test user is displayed and the deployment of subsequent commands stops. The commands can continue to be deployed only after the test user exits. However, the test user cannot exit during application deployment. As a result, the deployment times out.
Solution
Change the command to sudo -u test /bin/bash -c "shell command".
Parent topic: Running Shell Commands
Running Shell Commands FAQs
- 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
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.
more
