-
Notifications
You must be signed in to change notification settings - Fork 859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
calling exe from ssh on WSL2 will cause UtilAcceptVsock:244: accept4 failed 110
#8677
Comments
UtilAcceptVsock:244: accept4 failed 110
UtilAcceptVsock:244: accept4 failed 110
/logs |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
I've uploaded wsl logs. |
Thanks for the logs. The issue here is that sshd is not tied to a wsl.exe or wslhost.exe on the windows side (which handles interop requests). I have some thoughts on how to fix this, let me think about it a bit. |
looks like i have the same issue
WslLogs-2023-02-06_03-22-30.zip |
I'm facing this issue with Docker Desktop running from under WSL
But not always, randomly. |
I'm also getting same issue randomly
logs:
|
I'm getting this issue intermittently with Docker Desktop
|
everytime execute "code .", it's always give a prompt like this "<3>WSL (51) ERROR: UtilAcceptVsock:248: accept4 failed 110" |
I'm also randomly getting similar issues. In my case, I get an error( log is here: |
Interesting I'm receiving the same issue <3>WSL (20931) ERROR: UtilAcceptVsock:248: accept4 failed 110 |
here's my logs |
As with others above, I've started getting this infrequently with some work I'm doing with Docker - previously I've been using docker for just local development which was mainly My understanding is that the @OneBlue @benhillis I've not done any log collecting since it looks like there's a fair few already posted, but if either of you want to prioritize this I'm happy to be a guinea pig again to try and get any extra information you might need. |
In my case, enabling the interop option in wsl.conf solved the problem. https://learn.microsoft.com/en-us/windows/wsl/wsl-config#interop-settings
|
yeah man you get it. the problem about my wsl has been fix through this method |
I have no idea how this setting can solve the problem, because the value There is a value |
I get this on occasion and removing |
I had the same problem and @MitchellBot's solution fixed it for me. Thanks a lot. |
Bizarrely, I got this error too when running an
Also worth a shot for anyone else. Interestingly, this was only an issue for me after applying a Docker Desktop upgrade as well. Very odd. |
my hero! |
This worked for the similar issue that I had. The ERROR code was UtilAcceptVsock:250 instead of UtilAcceptVsock:246. |
Still getting this error when trying to run a llamafile in WSL2. @benhillis quick mention to see if this is on the team's radar? |
@bigfree is correct. Adding this to your config will cause a
This is what worked for me. |
To clarify, the error I receive is this: <3>WSL (5984) ERROR: UtilAcceptVsock:248: accept4 failed 110 It is not resolved by enabling or disabling Interop as I have tried both methods. |
I had the same issue and I remarked that most of WSL RAM was used |
From microsoft/wslg#1308 I am running NixOS 24.05 and this issue happens to me when trying to use win32yank.exe from WSL. |
Version
Microsoft Windows [Version 10.0.22000.795]
WSL Version
Kernel Version
5.10.102.1
Distro Version
Ubuntu 22.04
Other Software
Visual Studio/2022/Community
Repro Steps
setup & start the ssh server via systemctl
run some exe included in VisualStudio on ssh
Expected Behavior
run
cl.exe
successfullyActual Behavior
error
Diagnostic Logs
WslLogs-2022-08-03_15-54-53.zip
The text was updated successfully, but these errors were encountered: