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

[rye2020]

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:

Expected Behavior

update Ubuntu

Actual Behavior

see above

Diagnostic Logs

syslog not recording.

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

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:

• Failed to update from 23.10 to 24.04 on WSL2, by 2024.6.13 (#11694), similarity score: 0.73
• ubuntu 22_04 系统下载ubuntu desktop 下载报错，重启到期systemctl以及其他服务都不起来 (#11594), similarity score: 0.70

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

[rye2020]

similar issues not helpful

[rye2020]

jrm@OPX3050:~$ snap list
error: cannot list snaps: cannot communicate with server: timeout exceeded while waiting for response

[rye2020]

jrm@OPX3050:~$ sudo dpkg -C
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure or the configure menu option in dselect:
at Delayed job execution and batch processing

[rye2020]

jrm@OPX3050:~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up at (3.2.5-1ubuntu1) ...
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.
Failed to get properties: Transport endpoint is not connected
dpkg: error processing package at (--configure):
installed at package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
at
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

[rye2020]

jrm@OPX3050:~$ sudo apt install -f
[sudo] password for jrm:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up at (3.2.5-1ubuntu1) ...
Scanning processes...
No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

[rye2020]

Problem solved. The problem was apparently caused by partially installed/removed package. "sudo apt install -f" fixed that problem and all the symptoms and issues.

[rye2020]

Premature -
No syslog recording

[OneBlue]

/logs

[rye2020]

WslLogs-2024-08-12_22-00-14.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel found: 'C:\Users\jrmar\vmlinux'
Detected appx version: 2.3.17.0

[OneBlue]

Thank you @rye2020. I can see in the logs that you have a custom kernel in use. Can you capture logs of the issue being reproduced with the stock kernel ?

/logs

[rye2020]

When the problem arose, I installed a clean 22.04 LTS from the store. That distribution does not give any error. On the version producing the error, I have installed many apps over the years, but I have not myself changed the kernel. The 20.04 version was functioning fine. When I ran 'sudo do-release-upgrade' the problem came up immediately. In any event, the logs for 22.04 LTS would not be useful.

[rye2020]

jrm@OPX3050: sudo systemctl start cups
[sudo] password for jrm:
Failed to start cups.service: Transport endpoint is not connected
See system logs and 'systemctl status cups.service' for details.

jrm@OPX3050: sudo service cups start
Failed to start cups.service: Transport endpoint is not connected
See system logs and 'systemctl status cups.service' for details.

jrm@OPX3050: systemctl status
Failed to read server status: Transport endpoint is not connected

jrm@OPX3050:~$ sudo synaptic
[sudo] password for jrm:
Failed to start apt-news.service: Transport endpoint is not connected
See system logs and 'systemctl status apt-news.service' for details.
Failed to start esm-cache.service: Transport endpoint is not connected
See system logs and 'systemctl status esm-cache.service' for details.

jrm@OPX3050:~$ sudo pro enable esm-apps
One moment, checking your subscription first
Configuring APT access to Ubuntu Pro: ESM Apps
Updating Ubuntu Pro: ESM Apps package lists
Failed to start apt-news.service: Transport endpoint is not connected
See system logs and 'systemctl status apt-news.service' for details.
Failed to start esm-cache.service: Transport endpoint is not connected
See system logs and 'systemctl status esm-cache.service' for details.
^CInterrupt received; exiting. STALLED

jrm@OPX3050:~$ sudo systemctl start syslog
Failed to start syslog.service: Transport endpoint is not connected
See system logs and 'systemctl status syslog.service' for details.

[rye2020]

The solution at this link seemed to fix the problem: #8867

"

"

let me know if this is an incorrect or problematical fix.

[OneBlue]

let me know if this is an incorrect or problematical fix.

Interesting. I guess that makes sense this this would put systemd into a bad state. No concerns at all with this fix.

Closing since the issue is resolved