Using command ‘wsl’, there's no response.

[Ethan-Chen-plus]

Windows Version

10.0.25977.1000

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 1804

Other Software

'wsl' works well before, and I enjoy it. However, these days I can't open it.

Repro Steps

just using command wsl.

Expected Behavior

it should come into the ‘/home/kewei’ and show dedtails.

Actual Behavior

Diagnostic Logs

No response

the log file as the attachment:
WslLogs-2023-12-02_22-25-54.zip

I have tried these, but none of them works:

1. go to services.msc, make sure service LxssManager is running, if it is running already, restart it，after turn it on I can use wsl immediately.
2. Get-Service LxssManager | Restart-Service

[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!

Open similar issues:

• When I use command 'wsl' in powershell, there is no respond. (#9827), similarity score: 0.89
• No response when launching wsl in terminal (#10010), similarity score: 0.87
• WSL 2 sometimes has no response (#7503), similarity score: 0.84

Closed similar issues:

• can't use wsl command (#10728), similarity score: 0.87
• WSL doesn't works (#3296), similarity score: 0.87
• WSL doesn't works (#4265), similarity score: 0.87
• WSL is not responding to anything (#7885), similarity score: 0.87
• None of the WSL commands work on my machine (#9696), similarity score: 0.85
• WSL can not work (#5992), similarity score: 0.85
• WSL No Reponses without any error code. (#6385), similarity score: 0.84

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

[OneBlue]

/dump

[Ethan-Chen-plus]

I make my wsl run for 5 minutes with no response for Log collection is running. Please reproduce the problem and press any key to save the logs.

However File size too big: 25 MB are allowed, 53 MB were attempted to upload.
So I upload to repo:https://github.com/Ethan-Chen-plus/WslLogs/blob/main/WslLogs-2023-12-05_09-18-19.zip

[OneBlue]

Thank you @Ethan-Chen-plus. Looking at the dump it looks like things are stuck on the Linux side.

Let's see what's happening inside the VM. Can you please:

• Reproduce the issue
• Open a debug shell via: wsl.exe --debug-shell
• Paste the content of this script inside the debug shell
• Share the output on this issue
• The script will also output the path to a folder where it wrote some logs files, please share that folder here as well

This should help us understand where things are stuck

[DoctorWho8]

Thank you @Ethan-Chen-plus. Looking at the dump it looks like things are stuck on the Linux side.

Let's see what's happening inside the VM. Can you please:

• Reproduce the issue
• Open a debug shell via: wsl.exe --debug-shell
• Paste the content of this script inside the debug shell
• Share the output on this issue
• The script will also output the path to a folder where it wrote some logs files, please share that folder here as well

This should help us understand where things are stuck

Let's suppose I need to do all of that to debug a potential problem within the distribution which currently isn't available from the Microsoft Store. How therefore do I go about invoking the debug shell? This was returned from a regular Powershell routine:
"PS C:\Users\GCL\Desktop> wsl --debug-shell
The system cannot find the file specified.
Error code: Wsl/DebugShell/ERROR_FILE_NOT_FOUND"
And this was returned from an Administration level one:
"PS C:\Users\GCL\Desktop> cd ..
PS C:\Users\GCL> wsl --debug-shell
The system cannot find the file specified.
Error code: Wsl/DebugShell/ERROR_FILE_NOT_FOUND"

The strange part I was able to invoke the debug shell earlier, but wasn't able to paste the shell script described there.

[Ethan-Chen-plus]

I used command wsl.exe --debug-shell and pasted the

root@DESKTOP-3JRQ3HI [ ~ ]# set -ue

if [ $(whoami) != "root" ]; then
t --system)" script must be run as root in the system distro (via wsl.exe -u root
  exit 1
fi

ts=$(date +%F_%H-%M-%S)
target="/mnt/c/wsl-init-dump-$ts"

mkdir -p "$target"

tdnf install -y gdb

bash -c "cd $target && gcore -a \$(pgrep init)"

stack_log="$target/stacks.txt"
fd_log="$target/fd.txt"
for pid in $(pgrep init); do
  echo -e "\nProcess: $pid" >> "$stack_log"
  echo -e "\nProcess: $pid" >> "$fd_log"
  for tid in $(ls "/proc/$pid/task" || true); do
    echo "tid: $tid" >> "$stack_log"
echo "Logs and dumps written in $target"t"rueck_log" || true
Loaded plugin: tdnfrepogpgcheck
Refreshing metadata for: 'CBL-Mariner Official Extras 2.0 x86_64'
Refreshing metadata for: 'CBL-Mariner Official Microsoft 2.0 x86_64'
Refreshing metadata for: 'CBL-Mariner Official Base 2.0 x86_64'
mariner-official-base                  1285195 100%
Installing:
python3-libs     x86_64       3.9.14-8.cm2     mariner-official-base  30.73M    10.41M
python3          x86_64       3.9.14-8.cm2     mariner-official-base  45.46k    35.81k
mpfr             x86_64       4.1.0-2.cm2      mariner-official-base   2.72M     1.44M
zstd             x86_64       1.5.0-1.cm2      mariner-official-base 1009.51k  424.70k
elfutils-default-yama-scope noarch       0.186-1.cm2      mariner-official-base   1.77k    33.03k
zstd-devel       x86_64       1.5.0-1.cm2      mariner-official-base 171.69k    50.60k
xz-devel         x86_64       5.2.5-1.cm2      mariner-official-base 329.15k   100.59k
elfutils-libelf-devel x86_64       0.186-1.cm2      mariner-official-base  32.98k    39.95k
elfutils         x86_64       0.186-1.cm2      mariner-official-base   3.32M     1.19M
elfutils-devel   x86_64       0.186-1.cm2      mariner-official-base 190.29k    87.38k
gdb              x86_64       11.2-2.cm2       mariner-official-base  11.57M     4.97M

Total installed size:  50.08M
Total download size:  18.77M
python3-libs                          10919586 100%
python3                                  36668 100%
mpfr                                   1510228 100%
zstd                                    434888 100%
elfutils-default-yama-scope              33821 100%
zstd-devel                               51815 100%
xz-devel                                103009 100%
elfutils-libelf-devel                    40906 100%
elfutils                               1248214 100%
elfutils-devel                           89476 100%
gdb                                    5210872 100%
Testing transaction
Running transaction
Installing/Updating: python3-3.9.14-8.cm2.x86_64
Installing/Updating: python3-libs-3.9.14-8.cm2.x86_64
Installing/Updating: elfutils-libelf-devel-0.186-1.cm2.x86_64
Installing/Updating: xz-devel-5.2.5-1.cm2.x86_64
Installing/Updating: elfutils-default-yama-scope-0.186-1.cm2.noarch
Installing/Updating: zstd-1.5.0-1.cm2.x86_64
Installing/Updating: zstd-devel-1.5.0-1.cm2.x86_64
Installing/Updating: elfutils-0.186-1.cm2.x86_64
Installing/Updating: elfutils-devel-0.186-1.cm2.x86_64
Installing/Updating: mpfr-4.1.0-2.cm2.x86_64
Installing/Updating: gdb-11.2-2.cm2.x86_64
[New LWP 146]
0x00000000003e485d in ?? ()
Saved corefile core.1
[Inferior 1 (process 1) detached]
0x00000000003e485d in ?? ()
warning: target file /proc/152/cmdline contained unexpected null characters
Saved corefile core.152
[Inferior 1 (process 152) detached]
[New LWP 161]
0x00000000003e485d in ?? ()
warning: target file /proc/160/cmdline contained unexpected null characters
Saved corefile core.160
[Inferior 1 (process 160) detached]
0x00000000003e485d in ?? ()
Saved corefile core.162
[Inferior 1 (process 162) detached]
warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable.  Connect to gdbserver inside the container.
0x00000000003e485d in ?? ()
Saved corefile core.163
[Inferior 1 (process 163) detached]
Logs and dumps written in /mnt/c/wsl-init-dump-2023-12-06_15-16-04
root@DESKTOP-3JRQ3HI [ ~ ]#

But how to copy and open this folder?

[DoctorWho8]

I agree with @Ethan-Chen-plus here. What is also needed is that of feedback from the author. No not yourself, @Ethan-Chen-plus I mean any of the folks from Microsoft who happens to be involved here.

[OneBlue]

Thank you @Ethan-Chen-plus. /mnt/c maps to your C: drive in Windows so you should be able to just open the windows explorer from the start menu and grab the files from there.

[DoctorWho8]

@OneBlue I just repeated @Ethan-Chen-plus did and found the folder it created. However, since the VM is running properly, I did in fact see nothing there. Is this normal for a properly working image?

[Ethan-Chen-plus]

However I can't find it in my C: drive. I looked into the script.
I found that it just make a directory:

And since there is no '/mnt/c' before executing this script, I thought that's why I couldn't found it in 'C:'.

I think we should mount 'C:' to '/mnt/c' in wsl debugger before we execute the script. But how to mount?