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

How can I troubleshoot intermittent WSL2 system shutdown? #11251

Closed
1 of 2 tasks
rfay opened this issue Mar 4, 2024 · 7 comments
Closed
1 of 2 tasks

How can I troubleshoot intermittent WSL2 system shutdown? #11251

rfay opened this issue Mar 4, 2024 · 7 comments

Comments

@rfay
Copy link

rfay commented Mar 4, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.3155]

WSL Version

2.1.1.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

"Default distribution: Ubuntu; Default version: 2"

Distro Version

Ubuntu 22.04

Other Software

Docker Desktop windows 4.27.2

Repro Steps

Periodically the WSL subsystem on our test runners with Docker Desktop completely crashes. This is intermittent and can't give you repro steps.

However, when it happens all WSL2 distros have crashed, both the Ubuntu and the two Docker Desktop distros.

Expected Behavior

I would like to know how to debug this situation. What causes all of the WSL2 subsystem to crash, all distros to exit? How can I find out? Is it in the Event Log?

Actual Behavior

Thanks for any suggestions

Diagnostic Logs

Unfortunately, the collection of logs requires me to reproduce, and this is intermittent.

Copy link

github-actions bot commented Mar 4, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@OneBlue
Copy link
Collaborator

OneBlue commented Mar 5, 2024

Is WSL crashing or just shutting down ? I'd recommend to follow these instructions to collect the crash if WSL is indeed crashing.

If not, continuously running log collection until you can get a repro would be the best bet. /logs

@rfay
Copy link
Author

rfay commented Mar 5, 2024

Is WSL crashing or just shutting down ? I'd recommend to follow these instructions to collect the crash if WSL is indeed crashing.

That would be one of the questions: How can I tell the difference between crashing and shutting down? What I see after this event is that all (three) distros have exited, so wsl -l -v shows 3 stopped distros.

If not, continuously running log collection until you can get a repro would be the best bet

This happens ever few days, but not more often that that. The test runners run a number of jobs in those days. I'm not sure about the consequences of capturing an infinite amount of logs, or how they're going to be useful to you when we do. Willing to do it though...

@OneBlue
Copy link
Collaborator

OneBlue commented Mar 5, 2024

That would be one of the questions: How can I tell the difference between crashing and shutting down? What I see after this event is that all (three) distros have exited, so wsl -l -v shows 3 stopped distros.

The instructions I linked would be the best way: If you see a crash dump in the crash folders, then the WSL process crashed

@rfay
Copy link
Author

rfay commented Mar 5, 2024

I see enable automatic crash dump collection in that article, which put the dump in C:\crashes.

(I will do that)

But you say

If you see a crash dump in the crash folders

are you implying that there are other crash folders, or perhaps crash folders other than C:\crashes that I should be looking for?

@OneBlue
Copy link
Collaborator

OneBlue commented Mar 5, 2024

No there is only one crash folder

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-file it as a new issue.

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

2 participants