systemd-binfmt.service masked

[brasswood]

I noticed today that apt upgrade gave me the message Failed to restart systemd-binfmt.service: Unit systemd-binfmt.service is masked.

$ systemctl status systemd-binfmt.service
Warning: The unit file, source configuration file or drop-ins of systemd-binfmt.service changed on disk. Run 'systemctl>
○ systemd-binfmt.service
     Loaded: masked (Reason: Unit systemd-binfmt.service is masked.)
    Drop-In: /usr/lib/systemd/system/systemd-binfmt.service.d
             └─wsl.conf
     Active: inactive (dead)

$ ls -l /etc/systemd/system/systemd-binfmt.service
lrwxrwxrwx 1 root root    9 Sep 29  2023  systemd-binfmt.service -> /dev/null

What happened?

[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 [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'.

[brasswood]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[sirredbeard]

Odd that would happen in a package upgrade.

Have you tried the following?

sudo systemctl unmask systemd-binfmt.service
sudo systemctl start systemd-binfmt.service
systemctl status systemd-binfmt.service

and optionally:

sudo systemctl enable systemd-binfmt.service

if you want to run on each start.

[brasswood]

@sirredbeard Odd that I would get that error message from a package upgrade, or odd that a package upgrade would mask the service? I'm not actually sure what caused the service to get masked, though I'm fairly sure I didn't manually do it.

The link was made on September 29, 2023 so I'm looking through logs from that date to see if anything happened.

[brasswood]

Strangely, the link was made 11 seconds before journald logs begin. Could this have happened if I upgraded from WSL 1 to WSL 2 at that time?

I suppose I will unmask the service and hope that nothing breaks.

[OneBlue]

/logs

[microsoft-github-policy-service]

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

Thank you!

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