You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ever seen this before? I had rmate configured and working previously, but now when I do rmate on my remote host, it just hangs silently forever.
Sublime shows this in the log:
[rsub] Server running on localhost:52698...
And I don't see any error messages, and procexp shows the port open as I'd expect. I don't know of any configuration changes that would have broken it either. I ensured that the ssh tunnel is configured correctly and it certainly is.
Is there a way I can get diagnostic information on the sublime side or the rmate side? I tried the verbose switch to rmate and that did nothing.
The text was updated successfully, but these errors were encountered:
I should note that a few restarts of the ssh tunnel and of sublime 3 seems to have fixed this, but a single restart definitely didn't do the trick. I think there's some sort of network failure either in sublime or rmate, and I'm not getting any output to notify me about it. It doesn't seem to be anything obvious (no hung processes in ps | grep , port not in use by someone else). I've verified that it's not due to the port being closed - if I run rmate when I don't have the tunnel open, I get the error you'd expect.
Ever seen this before? I had rmate configured and working previously, but now when I do rmate on my remote host, it just hangs silently forever.
Sublime shows this in the log:
[rsub] Server running on localhost:52698...
And I don't see any error messages, and procexp shows the port open as I'd expect. I don't know of any configuration changes that would have broken it either. I ensured that the ssh tunnel is configured correctly and it certainly is.
Is there a way I can get diagnostic information on the sublime side or the rmate side? I tried the verbose switch to rmate and that did nothing.
The text was updated successfully, but these errors were encountered: