"systemctl status" error with systemd >= 250 (Ubuntu 24, Debian 12, ...)

[trallnag]

Windows Version

10.0.22631.3447

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

WSL 2

Kernel Version

5.15.146.1-microsoft-standard-WSL2

Distro Version

Debian Bookworm, but also affects other distros that have systemd version higher than 2.50, for example Ubuntu 24.04.

Repro Steps

Install Debian:

wsl --install Debian

Inside the distro enable systemd:

printf "[boot]\nsystemd=true\n" | sudo tee /etc/wsl.conf

Shutdown WSL from Windows:

wsl --shutdown

Again the distro:

PAGER= SYSTEMD_LOG_LEVEL=debug sudo systemctl status

You will see something like this:

Expected Behavior

● Metro
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Thu 2024-04-25 23:50:36 CEST; 8s ago
   CGroup: /
           ├─user.slice
           │ └─user-1000.slice
           │   ├─[email protected] …
           │   │ └─init.scope
           ...

Actual Behavior

Failed to dump process list for 'Metro', ignoring: Input/output error
● Metro
    State: running
    Units: 276 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Thu 2024-04-25 23:47:17 CEST; 44s ago
  systemd: 252.22-1~deb12u1
   CGroup: /

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

Open similar issues:

• systemd status fails output on Ubuntu (#8879), similarity score: 0.84
• systemd_249.11-0ubuntu3.10 seems to break user sessions on WSL2 (#10496), similarity score: 0.74

Closed similar issues:

• systemd upgrade failure (#8871), similarity score: 0.76
• [WSL2][systemd] Unable to upgrade systemd (#8847), similarity score: 0.74
• [PID 1 Error] "failed to connect to bus: no such file or directory" Windows 10, WSL 2, Debian - possible fix detailed (#10350), similarity score: 0.73

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

[trallnag]

WslLogs-2024-04-26_00-06-09.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.1.5.0

[trallnag]

Content-wise duplicate of #8879. It contains more information. But that issue's title only mentions Ubuntu, even though the issue appears with other distros as well.

Please consider closing this issue as duplicate, but adjusting the other issue's title and / or bumping it in priority for an initial review.