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.

Sign up for GitHub

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

Jump to bottom

Incompatible with systemd 257.3 #12597

Closed
1 of 2 tasks
potoo0 opened this issue Feb 18, 2025 · 8 comments
Closed
1 of 2 tasks

Incompatible with systemd 257.3 #12597

potoo0 opened this issue Feb 18, 2025 · 8 comments

Comments

@potoo0
Copy link

potoo0 commented Feb 18, 2025

Windows Version

Microsoft Windows [Version 10.0.26100.3194]

WSL Version

2.4.11.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

ArchLinux

Other Software

No response

Repro Steps

Updating systemd from 257.2 to 257.3 will cause systemctl status: degraded.

After rolling back to 257.2, it will work as expected.

sudo pacman -U /var/cache/pacman/pkg/{systemd-257.2-2-x86_64.pkg.tar.zst,systemd-libs-257.2-2-x86_64.pkg.tar.zst,systemd-sysvcompat-257.2-2-x86_64.pkg.tar.zst}

pacman.log:

[2025-02-17T15:59:53+0800] [ALPM] transaction started
[2025-02-17T15:59:53+0800] [ALPM] upgraded openssl (3.4.0-1 -> 3.4.1-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded systemd-libs (257.2-2 -> 257.3-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded curl (8.12.0-3 -> 8.12.1-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded runc (1.2.4-1 -> 1.2.5-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded docker (1:27.3.1-1 -> 1:27.5.1-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded docker-compose (2.32.4-1 -> 2.33.0-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded fzf (0.57.0-1 -> 0.59.0-1)
[2025-02-17T15:59:53+0800] [ALPM] upgraded gpgme (1.24.1-3 -> 1.24.2-1)
[2025-02-17T15:59:54+0800] [ALPM] upgraded python-click (8.1.7-4 -> 8.1.8-1)
[2025-02-17T15:59:54+0800] [ALPM] upgraded python-cryptography (44.0.0-1 -> 44.0.1-1)
[2025-02-17T15:59:54+0800] [ALPM] upgraded systemd (257.2-2 -> 257.3-1)
[2025-02-17T15:59:55+0800] [ALPM] upgraded systemd-sysvcompat (257.2-2 -> 257.3-1)
[2025-02-17T15:59:55+0800] [ALPM] upgraded yazi (25.2.7-1 -> 25.2.11-1)
[2025-02-17T15:59:55+0800] [ALPM] transaction completed
[2025-02-17T15:59:55+0800] [ALPM] running '20-systemd-sysusers.hook'...
[2025-02-17T15:59:55+0800] [ALPM] running '30-systemd-catalog.hook'...
[2025-02-17T15:59:55+0800] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2025-02-17T15:59:55+0800] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2025-02-17T15:59:55+0800] [ALPM] running '30-systemd-hwdb.hook'...
[2025-02-17T15:59:56+0800] [ALPM] running '30-systemd-restart-marked.hook'...
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for systemd-userdbd.service failed because the control process exited with error code.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status systemd-userdbd.service" and "journalctl -xeu systemd-userdbd.service" for details.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for systemd-journald.service failed because the control process exited with error code.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status systemd-journald.service" and "journalctl -xeu systemd-journald.service" for details.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for systemd-udevd.service failed because the control process exited with error code.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status systemd-udevd.service" and "journalctl -xeu systemd-udevd.service" for details.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for systemd-homed.service failed because the control process exited with error code.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status systemd-homed.service" and "journalctl -xeu systemd-homed.service" for details.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for systemd-resolved.service failed because the control process exited with error code.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details.
[2025-02-17T15:59:56+0800] [ALPM] running '30-systemd-sysctl.hook'...
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory
[2025-02-17T15:59:56+0800] [ALPM] running '30-systemd-tmpfiles.hook'...
[2025-02-17T15:59:56+0800] [ALPM] running '30-systemd-udev-reload.hook'...
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET]   Skipped: Device manager is not running.
[2025-02-17T15:59:56+0800] [ALPM] running '30-systemd-update.hook'...
[2025-02-17T15:59:56+0800] [ALPM] running 'dbus-reload.hook'...
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] Job for dbus-broker.service failed.
[2025-02-17T15:59:56+0800] [ALPM-SCRIPTLET] See "systemctl status dbus-broker.service" and "journalctl -xeu dbus-broker.service" for details.
[2025-02-17T15:59:56+0800] [ALPM] running 'texinfo-install.hook'...
[2025-02-17T15:59:56+0800] [ALPM] running 'vimdoc.hook'...
[2025-02-17T16:00:12+0800] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-02-17T16:00:12+0800] [PACMAN] synchronizing package lists
[2025-02-17T16:00:23+0800] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- extra/uv'
[2025-02-17T16:00:25+0800] [ALPM] transaction started
[2025-02-17T16:00:25+0800] [ALPM] installed uv (0.6.0-1)
[2025-02-17T16:00:25+0800] [ALPM] transaction completed
[2025-02-17T16:00:25+0800] [ALPM] running '30-systemd-update.hook'...

Expected Behavior

systemctl status:

$ sudo systemctl status
● DESKTOP-F6O165R
    State: running
    Units: 313 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
...

Actual Behavior

systemctl status:

$ sudo systemctl status
● DESKTOP-F6O165R
    State: degraded
    Units: 208 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 39 units
    Since: Tue 2025-02-18 16:32:15 CST; 16min ago
  systemd: 257.3-1-arch
   CGroup: /
           └─init.scope
             ├─  1 /sbin/init
             ├─  2 /init
             ├─  7 plan9 --control-socket 7 --log-level 4 --server-fd 8 --pipe-fd 10 --log-truncate
             ├─119 /init
             ├─120 /init
             ├─121 -zsh
             ├─122 "login -- wsl"
             ├─164 -zsh
             ├─260 sudo systemctl status
             ├─264 sudo systemctl status
             ├─265 systemctl status
             └─266 less

systemctl --failed:

$ sudo systemctl --failed
  UNIT                                     LOAD   ACTIVE SUB    DESCRIPTION
● dev-hugepages.mount                      loaded failed failed Huge Pages File System
● dev-mqueue.mount                         loaded failed failed POSIX Message Queue File System
● sys-fs-fuse-connections.mount            loaded failed failed FUSE Control File System
● sys-kernel-debug.mount                   loaded failed failed Kernel Debug File System
● sys-kernel-tracing.mount                 loaded failed failed Kernel Trace File System
● tmp.mount                                loaded failed failed Temporary Directory /tmp
● console-getty.service                    loaded failed failed Console Getty
● dbus-broker.service                      loaded failed failed D-Bus System Message Bus
● [email protected]                       loaded failed failed Getty on tty1
● ldconfig.service                         loaded failed failed Rebuild Dynamic Linker Cache
● lxcfs.service                            loaded failed failed FUSE filesystem for LXC
● systemd-boot-update.service              loaded failed failed Automatic Boot Loader Update
● systemd-homed.service                    loaded failed failed Home Area Manager
● systemd-journal-catalog-update.service   loaded failed failed Rebuild Journal Catalog
● systemd-journal-flush.service            loaded failed failed Flush Journal to Persistent Storage
● systemd-journald.service                 loaded failed failed Journal Service
● systemd-logind.service                   loaded failed failed User Login Management
● systemd-modules-load.service             loaded failed failed Load Kernel Modules
● systemd-remount-fs.service               loaded failed failed Remount Root and Kernel File Systems
● systemd-sysctl.service                   loaded failed failed Apply Kernel Variables
● systemd-sysusers.service                 loaded failed failed Create System Users
● systemd-tmpfiles-clean.service           loaded failed failed Cleanup of Temporary Directories
● systemd-tmpfiles-setup-dev-early.service loaded failed failed Create Static Device Nodes in /dev gracefully
● systemd-tmpfiles-setup-dev.service       loaded failed failed Create Static Device Nodes in /dev
● systemd-tmpfiles-setup.service           loaded failed failed Create System Files and Directories
● systemd-udev-load-credentials.service    loaded failed failed Load udev Rules from Credentials
● systemd-udevd.service                    loaded failed failed Rule-based Manager for Device Events and Files
● systemd-update-done.service              loaded failed failed Update is Completed
● systemd-update-utmp.service              loaded failed failed Record System Boot/Shutdown in UTMP
● systemd-user-sessions.service            loaded failed failed Permit User Sessions
● systemd-userdbd.service                  loaded failed failed User Database Manager
● wsl-binfmt.service                       loaded failed failed WSL binfmt restore
● dbus.socket                              loaded failed failed D-Bus System Message Bus Socket
● systemd-journald-audit.socket            loaded failed failed Journal Audit Socket
● systemd-journald-dev-log.socket          loaded failed failed Journal Socket (/dev/log)
● systemd-journald.socket                  loaded failed failed Journal Sockets
● systemd-udevd-control.socket             loaded failed failed udev Control Socket
● systemd-udevd-kernel.socket              loaded failed failed udev Kernel Socket
● systemd-userdbd.socket                   loaded failed failed User Database Manager Socket

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

39 loaded units listed.

Diagnostic Logs

No response
@github-actions GitHub Actions
Copy link

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

Closed similar issues:

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

@potoo0
Copy link
Author

potoo0 commented Feb 18, 2025

WslLogs-2025-02-18_18-01-15.zip

@potoo0 potoo0 mentioned this issue Feb 18, 2025
Open
@github-actions GitHub Actions
Copy link

Diagnostic information 
.wslconfig found
Detected appx version: 2.4.11.0

@OneBlue
Copy link
Collaborator

OneBlue commented Feb 18, 2025

Thank you @potoo0. Can you share the full journalctl output so we can see why the units are failing ?

@potoo0
Copy link
Author

potoo0 commented Feb 19, 2025

In fact, the journal also failed, so nothing was recorded.

@potoo0
Copy link
Author

potoo0 commented Feb 19, 2025 •
edited
Loading

tmux-cap-journalctl.log

I rolled backup to 257.2 on 02/18 17:20, and everything worked fine.

@zcobol
Copy link

zcobol commented Feb 19, 2025

@potoo0 systemd 257.3-1-arch is running okay on WSL:

[zcobol@texas ~]$ systemctl status --no-pager
● texas
    State: running
    Units: 315 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Wed 2025-02-19 13:26:28 PST; 32s ago
  systemd: 257.3-1-arch
   CGroup: /
           ├─init.scope
           │ ├─  1 /sbin/init
           │ ├─  2 /init
           │ ├─  8 plan9 --control-socket 7 --log-level 4 --server-fd 8 --pipe-fd 10 --log-truncate
           │ ├─192 /init
           │ ├─193 /init
           │ ├─194 -bash
           │ └─237 systemctl status --no-pager
---cut---

systemd info:

[zcobol@texas ~]$ systemctl --version
systemd 257 (257.3-1-arch)
+PAM +AUDIT -SELINUX -APPARMOR -IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE

WSL info:

[zcobol@texas ~]$ wslinfo --wsl-version
2.4.11

Test done with the latest Docker ArchLinux container exported to WSL and systemd-257.3 already installed.

@potoo0
Copy link
Author

potoo0 commented Feb 20, 2025

@potoo0 systemd 257.3-1-arch is running okay on WSL:
...

@zcobol
Thanks, I tested the antiz/archlinux-wsl1 and yuk7/ArchWSL2 image,
it turns out that only the yuk7 image has this problem.

Footnotes

  1. antiz/archlinux-wsl ↩

  2. yuk7/ArchWSL ↩

@potoo0 potoo0 closed this as completed Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@OneBlue @potoo0 @zcobol