New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically reconnect timed-out SSH connections #402
Comments
Jeff Forcier (bitprophet) posted: Thanks for the submission! The patch looks good. One of the upcoming releases will probably be network related so this fix will fit well there. on 2011-08-01 at 11:46am EDT |
Max Chervonec (webengineer.in.ua) posted: Glad to help! on 2011-08-02 at 09:55am EDT |
Any progress on this ticket? It doesn't seem to have made it into the main fabric repo yet. |
Toby, just in case you are interested how to workaround - try to use |
@webengineer is right that However, yea, I think I did intend for this to go in with the other stuff like timeout & reconnection attempts. @tow, what would really help is if you could evaluate how those three options -- keepalive, timeout & connection attempts -- intersect with the problem you are/were having, and with your proposed change. I think keepalive will prevent your exception from ever actually occurring, but not 100% sure. It's also possible that the way we implemented reconnections would similarly obviate the part of the code you modified. But that's just conjecture (I haven't time to repro on my end and test right now) and I'd still be happy to merge your patch if it looks like it fills a problem these other options don't cover. Thanks & sorry again :) |
@bitprophet, I am 95% sure that |
I'm also affected by the issue. Strangely enough, it doesn't seem to get resolved with Do you guys know if there's another workaround to this? I'm not sure if connection attempts is a good direction, since the initial SSH connection is established successfully - the problem is that it times out after a while. And I'm kind of suspicious of timeout, since most of the |
I'm hitting this issue on fabric 1.4.3, but setting
where when we hit that second block as user
Not really following who's who in this thread, but I don't think EDIT: I'm having trouble producing a small example that reproduces the problem, but can try harder if it would help. |
Ah, okay I figured out how to reproduce it; a Here is the task, run with
And here is the output with error:
Let me know if I should file a separate bug report. EDIT: the workaround I'm using is to call |
Hey @jberryman, I think the issue with that specific use case is that
I reckon we could update I'm also going to poke at the original patch in the description so I can finally close this poor ticket. |
@jberryman So, now that I have merged the original patch, it will theoretically also fix your problem, no |
Great! Won't be able to upgrade right away, but look forward to checking On Sat, Jan 26, 2013 at 12:54 PM, Jeff Forcier notifications@github.comwrote:
|
Sadly, I'm still getting this error. |
@MajorTal A) it's usually apropos to give details when you report such things ;) B) this hasn't actually been released yet, Fab 1.6.0 is still a few days away. Are you running the latest master branch? (If not, can you install from it & see if it fixes your specific issue?) Thanks! |
@bitprophet sorry, to clarify, have you tested on my task above that reproduces the issue that I posted or are you asking me to do that? |
Description
During continuous sessions with Amazon AWS instances it happens from time to time the "SSH session not active" exception.
I'd like to suggest webengineer@aab9fc0 workaround.
Originally submitted by Max Chervonec (webengineer.in.ua) on 2011-08-01 at 03:02am EDT
The text was updated successfully, but these errors were encountered: