I have a step like this:
- ssh -v user@host "./some_script.sh"
some_script.sh is fully executed (the last command is echo '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?
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,
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events