- 1 year ago
Rundeck [ssh-exec] can't find bash
If you're encountering an issue where Rundeck's SSH execution step cannot find the bash
command, it could be due to a couple of reasons:
Incorrect path: The
bash
executable might not be in the default system path used by Rundeck. To fix this, you can specify the full path to thebash
executable in your SSH execution step. For example:bash/bin/bash -c "your-command"
Replace
"your-command"
with the actual command you want to execute.Different remote shell: By default, Rundeck uses the remote shell specified in the SSH configuration of the target node. If the remote shell is not
bash
, Rundeck may not be able to find thebash
command. In such cases, you can try changing the remote shell in Rundeck's configuration tobash
. To do this, modify theframework.properties
file in Rundeck's configuration directory and set theframework.ssh-shell
property to/bin/bash
.propertiesframework.ssh-shell=/bin/bash
After making this change, restart the Rundeck service for the configuration to take effect.
Missing
bash
installation: If the target node does not havebash
installed, you'll need to install it before using it in Rundeck's SSH execution step. Use the appropriate package manager for your operating system to installbash
on the target node.
By addressing these possible causes, you should be able to resolve the issue of Rundeck's SSH execution step not finding the bash
command.