WSL2 UtilConnectUnix:513: connect failed 2

[ilovedumplings]

Windows Version

10.0.22631.4037

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

centos 7

Other Software

No response

Repro Steps

cannnot login into wsl2 of centos ,
it can be run when the compute power on , but after a while like 5 or 10 minutes ,cannot login wsl,but Open windows are not affected

Expected Behavior

wish can tell me how to slove it

Actual Behavior

wsl: 检测到 localhost 代理配置，但未镜像到 WSL。NAT 模式下的 WSL 不支持 localhost 代理。
<3>WSL (6533) ERROR: UtilConnectUnix:513: connect failed 2
<3>WSL (6533) ERROR: No such file or directory @init.cpp:365 (CreateProcessEntryCommon)
<3>WSL (6533) ERROR: CreateProcessEntryCommon:514: Create process failed

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Closed similar issues:

• I Can't Launch my WSL2 anymore (#7012), similarity score: 0.74
• WSL2 is running but terminal hangs when connet WSL (#5983), similarity score: 0.73
• WSL can't boot with Error code: Wsl/Service/0x8007274c (#10570), similarity score: 0.73
• Failed WSL2 login and problematic WSL1 login after win10 upgrade (#6880), similarity score: 0.72
• wsl2 won't start working? (#7768), similarity score: 0.71

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

[ilovedumplings]

When WSL has been running for a while, it starts to report errors. After I shut it down and restart it, WSL returns to normal.

[ilovedumplings]

[ilovedumplings]

Uploading WslLogs-2024-09-11_18-20-32.zip…

[ilovedumplings]

after the compute reboot,when the idea open,the error came out , it seems network prolems ,beacuse see the idea log , it show Unhandled control character: ACK like this

[ilovedumplings]

[OneBlue]

/logs

[ilovedumplings]

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 wsl-gh-logs@microsoft.com 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!

i provider it before

[OneBlue]

This link only points to this issue, it doesn't actually contain /logs

[ilovedumplings]

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 wsl-gh-logs@microsoft.com 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!

WslLogs-2024-09-12_15-11-39.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.2.4.0

[ilovedumplings]

Diagnostic information

.wslconfig found
Detected appx version: 2.2.4.0

[OneBlue]

Thank you @ilovedumplings. Once you get into this "bad state", can you use one of the open terminal to capture the output of dmesg and share it ? This will probably contain details about this issue.

Can you also share the output of ls /run/WSL, and htop once you get in this state ?

[ilovedumplings]

Thank you @ilovedumplings. Once you get into this "bad state", can you use one of the open terminal to capture the output of dmesg and share it ? This will probably contain details about this issue.

Can you also share the output of ls /run/WSL, and htop once you get in this state ?

thanks

[ilovedumplings]

the htop

[ilovedumplings]

this's the normal /run/WSL

[OneBlue]

Interesting, thank you @ilovedumplings. Do you see the same behavior with the latest pre-release version ?
You can install it via: wsl --update --release

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

Thank you!