PowerShell / PowerShell/Win32-OpenSSH
close - IO is still pending on closed socket. read:1, write:0, io:0000023DE45AF900
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
"OpenSSH for Windows" version
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2OpenSSH_for_Windows_8.6p1, LibreSSL 3.3.3
Server OperatingSystem
Ubuntu 18.04.5 LTS
Client OperatingSystem
Windows 10 Enterprise
What is failing
In my company, I have two PCs in the company network given by IT.
I usually open a CMD window and connect to remote Linux server with command ssh <account>@<server>.
However, I found that on my PC1, after disconnecting from remote Linux server, the ssh always shows the following error message at the last line:
close - IO is still pending on closed socket. read:1, write:0, io:0000023DE45AF900
But on my PC2, it never does that after disconnecting from the same remote Linux server.
I also tried to connect to other company remote Linux servers from the two PCs, but the results were the same as above.
So it seems that the problem is not on the remote side, but on the local side.
Besides, I tried different ssh toolchain versions.
The Windows 10 built-in ssh client version is OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2.
I downloaded the latest ssh toolchain version OpenSSH_for_Windows_8.6p1, LibreSSL 3.3.3, unzip it and set up PATH env variable, and tried again on my PC1.
Both versions shows the same error message after disconnection.
I would like to know how to fix this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the disconnect on Windows 10 Enterprise with OpenSSH_for_Windows 8.1p1 and 8.6p1 against an Ubuntu 18.04.5 LTS server, then compare the two PCs and the resulting socket behavior. Done means identifying a reproducible local cause and preventing the "IO is still pending on closed socket" message after disconnect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100