I have a step like this:
- step:
name: step
script:
- ssh -v user@host "./some_script.sh"
some_script.sh is fully executed (the last command is echo 'FINISHED')
FINISHED
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
This step is running until Bitbucket timeout.
Do you know what is wrong here? Shouldn't it stop and allow execute the following step after script reaches its end?
Hi Pawel,
Typically this happens because there are a number of background processes still using the input or output of the ssh connection. You can try the -f option but this often causes other problems with leaving orphaned processes on the remote machine. The best thing to do would be to try the command locally and see if it hangs there as well, then try some of the debugging tips from the answer here: https://superuser.com/questions/617252/why-does-ssh-hang-at-the-end-of-these-commands-and-how-can-i-make-it-exit
Hope this helps,
Matt Watson
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.