[OO Tip] Keeping TCP connection alive when terminated by load balancers
After an hour of inactivity the Secure Shell (SSH) connections are terminated by the load balancers. If a script is running on the target server this will also terminate. Is there a setting to keep the SSH session alive?
Please contact OO Support for assistance with this question as there is a suggested workaround but not a certified solution. Please mention this KB article.
Link to the document here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
I encountered the same problem, but it concerns in my case tcp connection.
A Bladelogic job is launched by a ras? and when the RAS receive the answer of Bladelogic, He tries to return the response to Central, but the LB has terminated the session.
How to force Central to send a TCP keep alive probe to inform LB not to terminate the session considered as inactive by LB ?
What was the workaroud suggested for this case ?
Thanks for your answer.
A suggested workaround would be to add parallel steps where the command is being executed in one lane. The other lane is using a loop to send a bogus command to the server (like: echo test > /dev/null) to keep the connection alive.
For this to work, the closeSession input needs to be set to false in all iterations of SSH Command on the two lanes.
Steps are as follows:
1. SSH Shell logon
2. Parallel Split Step
3. SSS Command
4. SSH Shell Logoff
HP Cloud Solution Support Engineer
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution. Also, if you liked this post please consider providing Kudos on the left side.