WSL: Failed to start apt-news.service: Transport endpoint is not connected

Windows Version

Microsoft Windows [Version 10.0.26257.5000]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Kernel version: 6.6.36.3-1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

updated Ubuntu by command ‘sudo do-release-upgrade’; prompt set to “normal” in /etc/update-manager/release-upgrades; after the release upgrade, unable to run ‘sudo apt update’; stalls after downloading files; syslog not recording; command ‘sudo reinstall rsyslog’ gives messages: TAKES MORE THAN ONE HOUR TO RUN

“Failed to reload daemon: Transport endpoint is not connected; Failed to retrieve unit state: Transport endpoint is not connected, invoke-rc.d: could not determine current runlevel; Failed to restart atd.service: Transport endpoint is not connected; See system logs and ‘systemctl status atd.service’ for details.; invoke-rc.d: initscript atd, action “restart” failed.; dpkg: error processing package at (–configure): installed at package post-installation script subprocess returned error exit status 1”; Setting up rsyslog (8.2112.0-2ubuntu2.2) … The user syslog' is already a member of adm’. Failed to reload daemon: Transport endpoint is not connected Failed to get unit file state for dmesg.service: Transport endpoint is not connected Failed to retrieve unit state: Transport endpoint is not connected dmesg.service is a disabled or a static unit not running, not starting it. Failed to get unit file state for rsyslog.service: Transport endpoint is not connected Failed to retrieve unit state: Transport endpoint is not connected rsyslog.service is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.10.2-1) … Errors were encountered while processing:

‘dmesg’ gives following: image

Expected Behavior

update Ubuntu

Actual Behavior

see above

Diagnostic Logs

syslog not recording.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16

Most upvoted comments

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 wsl-gh-logs@microsoft.com 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.