1. Command not found [SSH action]


Command not found


If you’re sure the execution command is correct, check the .bashrc file on the server. The file allows you to ignore commands executed in non-interactive mode. Make sure to remove or comment the config for non-interactive executions. It is usually preceeded with a line like this:

# If not running interactively, don't do anything

The config may look different depending on the system, for example:

# If not running interactively, don't do anything

case $- in

    *i*) ;;
      *) return;;


# If not running interactively, don't do anything
[ -z "$PS1" ] && return

If you are exporting PATH variable in ~/.bash_profile file, the variable will not be available in the SSH action because the file is run in interactive mode. In order for the action to run properly, move the exported PATH variable to ~/.bashrc file.

2. Host key verification failed


Host key verification failed.


Run the following line before the command:

ssh-keyscan <host> >> /root/.ssh/known_hosts

3. Base64: not found

If you want to run commands as a script, you need to install base64 on your server. Otherwise, please uncheck the option ‘Run as a script’.

4. Branches not getting synchronized in Buddy

If new commits to your external repository are not appearing in Buddy anymore, you can try to refresh the project. This will refresh all webhooks in the repository and fetch the current repository version, provided you still have permissions to do so.

  1. Go to the Code tab of the project
  2. Click Refresh in the right column

Location of Refresh buttonLocation of Refresh button

5. Error while loading shared libraries

Error message example: text error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory Solution Install the following packages in 'Customize Environment' tab: text apt-get update && apt-get install -y build-essential libpng-dev autoconf automake g++ libtool make nasm

Once done, run the pipeline with the 'Clear Cache' option selected.

6. SSH action: Command timeout after 10 minutes although a higher timeout is set in the action

Go to SSHD config on your server. On Linux it can be mostly found in the /etc/ssh/sshd_config file.

Apply a setting that will send the "NULL Packages" to the client in intervals shorter than 10 minutes. For example set:

ClientAliveInterval 120

Apart from that, you need to control the number of keep-alives sent to a client per session to:

ClientAliveCountMax 720

Restart the daemon sshd.