-
Notifications
You must be signed in to change notification settings - Fork 824
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
Network crashes - Connectivity to ubuntu guest fails after file upload / network stress #8598
Comments
/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! |
Pleasure, thanks for pointing out how to create a log file, wasn't aware of this option before. I have added the log output as requested. |
I created a second one, this time a bit more concise I hope. I did the following:
WslLogs-2022-07-13_11-54-02.zip This might be relevant, but not clear to me at this point. There's plan9 and docker activity (involving port 8080, which is exposing tomcat). Couple seconds later, the host network service is stopped?
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Microsoft Windows [Version 10.0.22000.778]
WSL Version
Kernel Version
5.10.102.1
Distro Version
Ubuntu-22.04
Other Software
Client: Docker Engine - Community
Version: 20.10.17
Repro Steps
Network connectivity seems to drop after stressing the network. I experienced this by
.war
file - invariably this failsAfter failure, I cannot ping my docker services or connect to my iperf3 server. After
wsl --shutdown
, network is restored (until it fails again). Services remain running in WSL though: I can access them from within Ubuntu, just not from Windows.Expected Behavior
Network connectivity remains, even when stressed.
Actual Behavior
Network fails.
Diagnostic Logs
Not sure how to proceed - is it possible to generate a network-stack debug log for WSL?
The text was updated successfully, but these errors were encountered: