Skip to content
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

wsl unable to start. #10679

Closed
1 of 2 tasks
Tapir28 opened this issue Oct 25, 2023 · 5 comments
Closed
1 of 2 tasks

wsl unable to start. #10679

Tapir28 opened this issue Oct 25, 2023 · 5 comments

Comments

@Tapir28
Copy link

Tapir28 commented Oct 25, 2023

Windows Version

Microsoft Windows [Version 10.0.22635.2500]

WSL Version

2.0.6.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Ubuntu 22.04

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

From powershell, I shutdown and then try to restart wsl.

wsl --shutdown
wsl

Expected Behavior

wsl stops, and starts again.

Actual Behavior

(Ubuntu was updated to 22.04 from 20.04. The name distribution name is not accurate.)

PS C:\Users\Emma> wsl -l -v
NAME STATE VERSION

  • Ubuntu-20.04 Running 2
    PS C:\Users\Emma> wsl --shutdown
    PS C:\Users\Emma> wsl
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    Error code: Wsl/Service/0x8007274c
    PS C:\Users\Emma> wsl
    The operation timed out because a response was not received from the virtual machine or container.
    Error code: Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT

Diagnostic Logs

WslLogs-2023-10-25_11-08-30.zip

@benhillis
Copy link
Member

@OneBlue - could you take a look please? Looks like it might be related to the change you made around init sockets.

@OneBlue
Copy link
Collaborator

OneBlue commented Oct 25, 2023

Thank you for reporting this @Tapir28. I'm not seeing the entire startup context in the logs. Can you try to:

  • Start log collection
  • Run wsl --shutdown
  • Reproduce the issue
  • Stop log collection

And share those logs ? /logs

@microsoft-github-policy-service
Copy link
Contributor

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:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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!

@akulbe
Copy link

akulbe commented Oct 27, 2023

@benhillis I hesitate to create another bug, my system exhibits a sort of hanging behavior… like no response from simply trying to start wsl or run wsl -l -v.

I collected logs. If this needs to be a new one, let me know.

wsl --version returns:

WSL version: 2.0.6.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22635.2552

WslLogs-2023-10-27_08-07-15.zip

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants