Error: (SSH) Channel open failure: open failed #3020
Replies: 5 comments
-
|
I've had a similar issue since using VSCode. According to my research a big difference between RDi and VSCode is how it connects, RDi would keep locks on files until you close, while VSCode opens multiple connections, or something to that effect. I'd also like more info on this. |
Beta Was this translation helpful? Give feedback.
-
|
@RPGLE-Logic , roughly:
As for the But there is a update in the making that should hopefully prevent this from happening. See #2940 |
Beta Was this translation helpful? Give feedback.
-
|
@sebjulliand , thanks for the prompt feedback and if it helps I can replicate the error. |
Beta Was this translation helpful? Give feedback.
-
|
I am going to convert this to a discussion. It's an SSH limitation and has been around since the early days. Fingers crossed we can combat it with Mapepire! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I've been noticing this problem for a while now.
Sometimes it happens when I try to open a new member, sometimes when saving a member and as in the case above, I noticed that a copybook hadn't loaded in the background and found this log in the developer client console.
I'm pretty sure this occurs when Code for i is dealing with a number of file requests and most commonly when it's pulling down include files in the background after opening a member.
This occurs when I'm working with source members and I am nearly always working over a remote VPN connection so there may be some network latency involved in my connection.
It is intermittent. If it happens whilst attempting to open a member, if I try again it generally works fine.
Active extensions
Remote system
Enabled features
Shell env
Variants
{ "american": "#@$", "local": "#@£", "qsysNameRegex": {} }Beta Was this translation helpful? Give feedback.
All reactions