While working to update four Linux servers last week I
completed the updates on one server w/o an issue and while logged in as root I
restarted the one server and RDM froze and shutdown closing all the tabs I had
open to the other servers. Is there a setting that I may have missed that would
prevent a restart of an SSH connection from impacting the entire RDM
application and additional connections?
Hello Felix,
I want to ensure I fully understand your issue.
To clarify, you are using RDM on Windows to connect to four servers running Linux right?
And when you connect to these Linux servers using an SSH shell entry, executing the “reboot” command causes the local RDM on Windows to crash?
If this is the scenario, I'd like to inform you that this is a known issue, and our developers are actively working to resolve it.
If I've misunderstood any part of your problem, please feel free to rephrase or clarify. Alternatively, we can arrange a session to ensure we're on the same page.
Best regards,
Carl Marien
Hello Carl,
My apologies for not being more specific. Yes, I am running RDM on windows to administer multiple Linux servers. The application crashed on me while I was rebooting the first server.
Thank you for responding and letting me know it is on the developer list!
Felix.
This is a glaring RDM issue that persists for years.
I've tried 2023.3.37.0 this week, still the same.
Easy way to reproduce:
Et voila, SSH session hangs, tabbed interface becomes unresponsive. The only thing you could do is to close the broken session via context menu in Navigation tree.
Rant time. It's like every RDM user and developer doesn't use laptops (you know, close the lid without closing any opened RDM sessions and go somewhere, like laptop users are able to do), and every RDM user and developer has a perfect connection with 100% uptime to every single remote host. Otherwise I can't explain why Google doesn't show anything about it.
Hi @apthyzen
It is normal behaviour for an SSH session to become unresponsive after the wifi connection is deactivated. This effectively closes the TCP connection, and reactivating the wifi will not remake the connection. Probably that the "Disconnect action" option of your SSH entry is set to "Keep open" (which means to keep the terminal open) and that the "Display error messages" option is set to "No". Normally, with those settings, the tab name will eventually display it is disconnected without any error messages, but TCP being what it is, it can take minutes before it gets updated. Nonetheless, you should be able to right click in the tab and select "Reconnect" in the contextual menu. If this is unresponsive as well and you can't select other tabs, this is not normal and not something we experienced here in our tests. We then would need more details on the settings of your entry to help you on the matter.
Hoping this clarifies the situation.
Regards
Denis Vincent
Hello,
The freeze issue (caused by having an SFTP connection alongside an SSH session) is now fixed internally and will be included in beta version 2024.1.8.0.
Regards
Jonathan Del Signore