Parameters Contain Backslashes (\)
Symptoms
When a host-related application is deployed, an error message is displayed.
The following takes a path as an example.
- The deployment fails due to the \b characters.
Figure 1 Log information
- The deployment fails due to the \f characters.
Figure 2 Log information
- The deployment fails due to the \r characters.
Figure 3 Log information
- The deployment fails due to the \t characters.
Figure 4 Log information
- The deployment fails due to the \n characters.
Figure 5 Log information
Cause Analysis
The deployment failure is caused by the use of escape characters that have special meanings.
Solution
- Method 1: Avoid using special escape characters.
- Method 2: Use forward slashes (/) instead of backslashes (\).
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.
more