Failed: SSHProtocolFailure: channel is not opened in v4.9.0

[liberodark]

Describe the bug When i using SSH Have connection timeouts with the following error: Failed: SSHProtocolFailure: channel is not opened. (not all the times sometimes it works it happened suddenly.)

My Rundeck detail

• Rundeck version: 4.9.0
• install type: RPM
• OS Name/version: AlmaLinux 8
• DB Type/version: MariaDB

Java version :

openjdk 11.0.18 2023-01-17 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.18.0.10-2.el8_7) (build 11.0.18+10-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.18.0.10-2.el8_7) (build 11.0.18+10-LTS, mixed mode, sharing)

To Reproduce Steps to reproduce the behavior:

1. Run echo "Test Me" on Commands with 32 servers :

2. Click on Run

3. Issue : Failed: SSHProtocolFailure: channel is not opened.

Expected behavior Im using only keypair for connect in SSH with Rundeck.

Screenshots ssh (32/33 sec)

openssh/executor (18/19 sec)

Desktop :

• OS: Linux
• Browser Firefox
• Version 109

Additional context I changed the Connection Timeout & Command Timeout to 3000 it works. (Workaround 1) But if I put 0 or lower it doesn't work. So I had to switch to openssh/executor which is faster and no have this issue. (Workaround 2)

I remain at your disposal if you have any further questions.

Best Regards

[rpo-fr]

i have similar problem

[bla-ckbox]

Hello,

I encountered a similar problem using version 4.3 with the official Docker image. Regarding the context, we were already using Rundeck, but it was a very old version with a standard installation.

In the end, we were able to solve the problem with two changes, You need to modify this files:

• On the Rundeck container, edit the _/etc/ssh/sshconfig (ssh client config) to add "SendEnv RD_*"
• On nodes, edit the _/etc/ssh/sshdconfig (sshd daemon config) to add "AcceptEnv RD_*" , reload sshd

Be careful with old Rundeck versions; only variables like RDOPTION was required, so today Rundeck requires it to be RD_*. Edit old sshd_config accordingly.

BLA