WSL2 - Failed to (auto)start systemd units on boot | /sbin/init failed #11822
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt: 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 View similar issuesPlease 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:
|
Diagnostic information |
|
See #8879 |
|
Thank you @0Styless. Let's see if this is a timeout issue. Can you add: To |
|
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! |
Windows Version
Microsoft Windows [Version 10.0.22621.3737]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps
Upgrade Ubuntu 22.04 to Ubuntu 24.04 with
do-release-upgradeExpected Behavior
Everything works fine, systemd services would start as before.
Actual Behavior
Systemd services do not start correctly. In
dmesgI can see[ 11.253131] WSL (2) ERROR: WaitForBootProcess:3342: /sbin/init failed to start within 10000(see attached diagnostic logs).After WSL / distro is started, I tried the following:
As you can see, the status is inactive (dead), expected behavior is that the service is up & running.
I also can start the service "per hand":
$ sudo systemctl start named $ sudo systemctl status named 121ms Mon 15:39 ● named.service - BIND Domain Name Server Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; preset: enabled) Active: active (running) since Mon 2024-07-22 15:39:26 CEST; 2s ago Docs: man:named(8) Main PID: 1750 (named) Status: "running" Tasks: 50 (limit: 19061) Memory: 22.1M () CGroup: /system.slice/named.service └─1750 /usr/sbin/named -f -u bind Jul 22 15:39:26 A61001309 named[1750]: zone localhost/IN: loaded serial 2 Jul 22 15:39:26 A61001309 named[1750]: zone local.net/IN: loaded serial 2023060609 Jul 22 15:39:26 A61001309 named[1750]: zone local.net/IN: sending notifies (serial 2023060609) Jul 22 15:39:26 A61001309 named[1750]: zone wsl.local/IN: loaded serial 2023081501 Jul 22 15:39:26 A61001309 named[1750]: zone wsl.local/IN: sending notifies (serial 2023081501) Jul 22 15:39:26 A61001309 named[1750]: zone showcaseakdb.net/IN: loaded serial 2024070102 Jul 22 15:39:26 A61001309 named[1750]: zone showcaseakdb.net/IN: sending notifies (serial 2024070102) Jul 22 15:39:26 A61001309 named[1750]: all zones loaded Jul 22 15:39:26 A61001309 named[1750]: running Jul 22 15:39:26 A61001309 systemd[1]: Started named.service - BIND Domain Name Server.Diagnostic Logs
dmesg:The text was updated successfully, but these errors were encountered: