processes started by systemd in wsl are orphaned if wsl crashes

[aquirdTurtle]

Windows Version

Microsoft Windows [Version 10.0.22631.2715]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.133.1-microsoft-standard-WSL2 (root@1c602f52c2e4) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Oct 5 21:02:42 UTC 2023

Distro Version

22.04

Other Software

No response

Repro Steps

• WSL crashes for some reason (looking into this, will try to actively cause crash to reproduce better). wsl -l --running shows no running distributions.
• Process created by systemd in wsl is still visible hogging a tcp port in "resource monitor".
• If I try to restart WSL to restart my program, I get port-in-use errors.
• If I kill the process visible in resource monitor first (using `taskkill \pid 1234 \f), I can restart my programs in the new wsl instance correctly.

I can develop some more rigorous reproducing steps if needed, but I also just wanted to query at some level if this was known / expected behavior.

Expected Behavior

If WSL crashes, I'd expect the processes it starts to crash as well, otherwise seems impossible to interact with the related processes and you get strange errors. For a while I thought it was an issue with WSL still effectively running in the background but now It's this "orphaned process" issue.

Actual Behavior

The processes started by wsl live on and cause issues trying to restart things.

Diagnostic Logs

No response

[github-actions]

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!

Closed similar issues:

• catastrophic failure after enabling systemd in wsl.conf (#8981), similarity score: 0.81
• WSL does not start when Systemd is enabled (#8856), similarity score: 0.81
• WSL Can't start after enabling systemd (#9477), similarity score: 0.79
• WSL2 + WSLg + systemd support Conflict (#9257), similarity score: 0.79
• systemd still not working on wsl2 (#4202), similarity score: 0.78

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

[OneBlue]

/logs

[microsoft-github-policy-service]

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

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

[microsoft-github-policy-service]

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!