Forum / Remote Desktop Manager - Support

SSH/terminal windows crashing in latest RDM

  • Create an Issue
  • Cancel

Hello,

Since upgrading to the latest 64bit Windows client yesterday, I am finding that some SSH/terminal windows close/quit/crash/exit of their own accord.

For instance, I have an SSH/terminal window open where I am watching server logs. After an undetermined amount of time, the SSH/terminal window just dies and closes.

I watch server logs every single day as part of my job, so this definitely wasn't happening before the upgrade.

I am wondering whether some text buffer is getting full and crashing the terminal client/window?

Any help or advice would be appreciated.

Kind regards

Clock7 mths

I have checked the [Advanced] settings for the session, by the way, and it isn't set to close after any amount of time.

Clock7 mths

I have found that this isn't caused by a buffer issue as previously suspected.

I had a SSH terminal window open, where I was editing a file on a linux server (using VIM). I left my desk, and when I returned, and switched to the RDM application window, my terminal session had gone.

This is now a major issue, as it means I am losing work (the file was half-way through being edited).

The problem is also definitely nothing to do with session time-out, as my other two terminal sessions were still running (one of which was against the same server).

Clock7 mths

Hello,

Is this an issue with RDM or not?
Sorry, not sure to understand what is the issue exactly.

Best regards,



Jeff Dagenais

signaturesignature

Clock7 mths

Yes, this is with RDM Enterprise Edition v2019.1.20.0 64-bit

Clock7 mths

Hello,

I took the liberty of opening a ticket under your name in order to provide more information about this issue to our engineering department, the ticket number is Devo-3373.

I will contact you using this ticket until this issue has been solved. Once a fix is found, I will update this forum thread as well.

Best regards,



James Lafleur

signaturesignature

Clock7 mths

Hello

I have exactly the same, after upgrading to RDM Enterprise Edition v2019.1.20.0 64-bit for "ssh shell" very often either the session is self-closed, or RDM crash.

Most often, it crashes when displaying large-sized text files. In the near future, he will provide the crash error code.


My OS is win 7 64bit.

Clock7 mths

I cat 9KB file and get crash


Signature of the problem:
Problem event name: APPCRASH
Application name: RemoteDesktopManager64.exe
Application version: 2019.1.20.0
Application time stamp: 5cdb2a47
Module name with error: StackHash_4821
Module version with error: 6.1.7601.24441
Module timestamp with error: 5cb9356e
Exception code: c0000374
Exception offset: 00000000000bf302
Operating system version: 6.1.7601.2.1.0.256.48
Regional settings identifier: 1045
Additional information 1: 4821
Additional information 2: 4821ced5e5f5650124329f1b06aa3984
Additional information 3: b339
Additional information 4: b339919afd6404e2c48e8da90748f0c0

Clock7 mths

now crash different dll


Signature of the problem:
Problem event name: APPCRASH
Application name: RemoteDesktopManager64.exe
Application version: 2019.1.20.0
Application time stamp: 5cdb2a47
The name of the module with error: DevolutionsProtocols.dll
Module version with error: 0.0.0.0
Module timestamp with error: 5cdae757
Exception code: c0000005
Exception offset: 00000000000fad27
Operating system version: 6.1.7601.2.1.0.256.48
Regional settings identifier: 1045
Additional information 1: 6924
Additional information 2: 692415f831a16bd1b25fbc0ea351c94f
Additional information 3: 31dd
Additional information 4: 31ddc538fc4a7ac74e72711170a24fe3

Clock7 mths

@l07,

Do you encounter the same issue on a Windows 10 computer?

Best regards,



Jeff Dagenais

signaturesignature

Clock7 mths

+1

RDM Free v2019.1.7.0 64-bit
Windows 10 x64 1803 (17134.765)

SSH window close unexpected


here is my log for this session:

[22.05.2019 11:43:58] Setting up connection

[22.05.2019 11:43:58] Connecting as xxx
[22.05.2019 11:43:58] SSH banner: SSH-2.0-OpenSSH_8.0
[22.05.2019 11:43:58] Sending kex init
[22.05.2019 11:43:58] Received kex init
[22.05.2019 11:43:58] Selected algorithms: curve25519-sha256, ssh-ed25519, chacha20-poly1305@openssh.com, chacha20-poly1305@openssh.com, implicit by cipher, implicit by cipher, none, none
[22.05.2019 11:43:58] Sending Ed25519 kex init
[22.05.2019 11:43:58] Received Ed25519 kex reply
[22.05.2019 11:43:58] Successfully authentified server
[22.05.2019 11:43:58] Sending new keys message
[22.05.2019 11:43:58] Sending userauth service request
[22.05.2019 11:43:58] Received new keys message
[22.05.2019 11:43:58] Received service accepted message
[22.05.2019 11:43:58] Sending userauth init request
[22.05.2019 11:43:58] Received userauth failure: publickey,keyboard-interactive
[22.05.2019 11:43:58] Starting interactive authentication
[22.05.2019 11:43:58] Sending userauth interactive request
[22.05.2019 11:43:58] Received userauth info request: / {Password: }
[22.05.2019 11:43:58] Sending userauth interactive response
[22.05.2019 11:43:58] Received userauth info request: / {}
[22.05.2019 11:43:58] Sending userauth interactive response
[22.05.2019 11:43:58] Received userauth success
[22.05.2019 11:43:58] User authenticated successfuly by password interactive
[22.05.2019 11:43:58] Sending session channel open request: 0/-
[22.05.2019 11:43:58] Received global request: hostkeys-00@openssh.com , no need to reply
[22.05.2019 11:43:58] Received channel open confirmation: 0/0 WS 200000/0 MPS 32000/32768
[22.05.2019 11:43:58] Sending pty request: 0/0 xterm
[22.05.2019 11:43:58] Received channel success: 0/0
[22.05.2019 11:43:58] Sending environment variable request: 0/0
[22.05.2019 11:43:58] Received channel success: 0/0
[22.05.2019 11:43:58] Sending shell request: 0/0
[22.05.2019 11:43:58] Received channel success: 0/0
[22.05.2019 11:44:16] Received unknown channel request: 0/0 keepalive@openssh.com
[22.05.2019 11:44:21] Received unknown channel request: 0/0 keepalive@openssh.com
[22.05.2019 11:44:26] Received unknown channel request: 0/0 keepalive@openssh.com
[22.05.2019 11:44:31] Sending channel close request: 0/0
[22.05.2019 11:44:31] Disconnecting

Before I used version 14.1.2.0 without any problem.

Clock7 mths

Ok, it seems there is more than one issue here: the last log shows there is a problem with an OpenSSH extension for keep alive. This should be fixed quickly.

There seems to be another problem with large amount of data output by the server. I do not experience this problem, even with an 80 KB file, Maybe there are other factors in play: like the scroll back size, or the terminal dimensions. Is the file content displayed is standard text? Do you use special options of the cat command?

In the mean time you can use the legacy terminal, but I'm sure our tech support already made the suggestion.

Regards

Denis Vincent

signaturesignature

Clock7 mths

In my case it's usually normal cat, crontab -l, history, nothing special

And sometimes the program works well for 30 minutes, after which it will hang 3 times in 10 minutes with the same commands.
In the session settings nothing has changed.


Now i'm searching win 10 machine to check.

Clock7 mths

dvincent wrote:

Ok, it seems there is more than one issue here: the last log shows there is a problem with an OpenSSH extension for keep alive. This should be fixed quickly.

Look like, i disable ClientAliveInterval and session not hang now. Logs not have "Received unknown channel request" records now. I use OpenSSH 8.0p1.

Clock7 mths

i check on win10 build 1803

source: .NET Runtime

Application: RemoteDesktopManager64.exe
Architecture version: v4.0.30319
Description: the process was terminated due to an unhandled exception.
Information about the exception: exception code: c0000005, exception address: 00007FFF2C24C257


source: aplication

The name of the application causing the error: RemoteDesktopManager64.exe, version: 2019.1.21.0, time stamp: 0x5ce352fe
The name of the module causing the error: DevolutionsProtocols.dll, version: 2019.5.17.2, time stamp: 0x5cdf1146
Exception code: 0xc0000005
Error offset: 0x00000000000fc257
The identifier of the process causing the error: 0x740
The time the application started causing the error: 0x01d51135ee5a9c9e
The application path causing the error: C: \ Program Files (x86) \ Devolutions \ Remote Desktop Manager \ RemoteDesktopManager64.exe
Path of the module causing the error: C: \ Program Files (x86) \ Devolutions \ Remote Desktop Manager \ x64 \ DevolutionsProtocols.dll
Report ID: 4b8ccf2b-460b-40f7-b36e-c917295830c9
The full package name causing the error:
The application identifier relative to the error package:

Clock7 mths


new version has the same bug

i do only cat /etc/passwd | grep X


Podpis problemu:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: RemoteDesktopManager64.exe
Wersja aplikacji: 2019.1.25.0
Sygnatura czasowa aplikacji: 5ce9516d
Nazwa modułu z błędem: DevolutionsProtocols.dll
Wersja modułu z błędem: 2019.5.24.1
Sygnatura czasowa modułu z błędem: 5ce7ffff
Kod wyjątku: c0000005
Przesunięcie wyjątku: 00000000000fc317
Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.48
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: 6924
Dodatkowe informacje 2: 692415f831a16bd1b25fbc0ea351c94f
Dodatkowe informacje 3: c168
Dodatkowe informacje 4: c1686e4588a748b4edadc60bc8a323b3

Clock6 mths

Hi,

Sorry, I did not work on this issue. I am not able to reproduce your bug, but maybe we can try something: we can use session recording, this could allow me to playback the same output that causes your crash in my debugging environment.

To enable recording, in the SSH shell entry dialog, select in the left pane "Session recording", then in the right pane, set mode to either "Optional" or "Required", you can set "Destination" to "Custom" and enter the directory path in the edit field below it. Do the same for "Filename".

Once that is done, run your session and do the required command to reproduce the problem. You can send me the resulting .trp file to dvincent@devolutions.net. Remember I will playback that file, so make sure there is no sensitive information you do not want me to see.

Thanks for your time, and again sorry for the late comeback.

Denis Vincent

signaturesignature

Clock6 mths

It tests the latest versions on windows 7 and 10 - 32 and 64 bit.

On windows 7 it happens to me often on windows 10 less often
Sometimes it works 3-4 hours and nothing happens, sometimes it may hang up 3 times in 20 minutes. The commands are the simplest type of: history, crontab -l, cat somfile | grep string. And I can not achieve repeatability that exactly one command causes a problem.

As for windows 7, the last change that was in the system is an update to all patches on May 2019.


Maybe I have bad versions of .net runtime (v4.0.30319)


I'll try to record someting.

Clock6 mths

Hi all,

Thanks for addressing this bug. I can report that v2019.1.25.0 64-bit is no longer dropping my SSH/terminal sessions smile

Clock6 mths

In the v2019.1.25.0 64-bit version, the problem still occurs. I was not able to record the session.
At the moment I came back to 14.1.3.0 64bit

I noticed differences between 14.1.3.0 and 2019.1.20 and newer ones.
In windows I use the increased dpi value, in version 14.1.3.0 64bit, the font actually looks bigger.
In version v2019.1.20.0 and newer, the font looked normal

Maybe it's a different version of the bug from version 2019.1.25, where it was fixed
"Fixed a HDPI crash at startup with the Legacy theme"

Clock6 mths

This is still an issue.

Affects me on login, as my shell profile sets up a dynamic window title which seems to cause this (used by putty, and traditional xterm/rxvt/etc). Disabling that line in my profile allows me to log in, but I seem to be unable to reproduce the crash by manually emitting the escape strings afterwards.


Clock30 days

That's interesting, could you tell me what is that line? I will set it up in one of our test servers and try it out. It would be helpful to know what kind of server you are connecting to (example: openSSH on Ubuntu).

Regards.

Denis Vincent

signaturesignature

Clock30 days


I'm having issue with SSH as well. After a while the terminal just hangs. Even closing the session makes RDM unresponsive for a while. Everything is default except I have TCP KeepAlives enabled.


Using 2019.1.41.0 64-bit on Windows 10 Pro 1809.

Clock14 days

@etienne01,

What type of data source are you running? If you are using a local data source like SQLite or XML as example, could you try to update RDM to the latest release, which is 2019.2.15.0?

You can download this release of RDM here
https://remotedesktopmanager.com/home/download

Best regards,



Jeff Dagenais

signaturesignature

Clock14 days

@Jean-Francois Dagenais

It's a local data source. I've updated to the latest, worked with it for a bit and it happened again. I thought the session was timing out but it actually crashed while I was working in a SSH session. At the time, I was hitting tab to autocomplete, if it matters.

Thanks

Clock12 days

Hello,

Could you enable the verbose feature like explained in this article and send us the logs?
https://devolutions.atlassian.net/servicedesk/customer/portal/1/article/608731251

Best regards,



Jeff Dagenais

signaturesignature

Clock12 days