Bug#1068487: man-db: Failed to get unit file state for man-db.service: Transport endpoint is not connected

[Colin Watson]

Control: reassign -1 systemd

On Sat, Apr 06, 2024 at 11:18:55AM +0800, Bo YU wrote:
> Today upgraded my riscv64 sid , I got:
> 
> ```
> Setting up man-db (2.12.1-1) ...
> Updating database of manual pages ...
> Reload daemon failed: Transport endpoint is not connected
> 
> Failed to get unit file state for man-db.service: Transport endpoint is not connected
> Failed to retrieve unit state: Transport endpoint is not connected
> man-db.service is a disabled or a static unit not running, not starting it.
> Failed to get unit file state for man-db.timer: Transport endpoint is not connected
> Failed to retrieve unit state: Transport endpoint is not connected
> man-db.timer is a disabled or a static unit not running, not starting it.
> ...
> Setting up openssh-sftp-server (1:9.7p1-4) ...
> Setting up openssh-server (1:9.7p1-4) ...
> Reload daemon failed: Transport endpoint is not connected
> Failed to get properties: Transport endpoint is not connected
> Reload daemon failed: Transport endpoint is not connected
> Failed to get unit file state for ssh.service: Transport endpoint is not connected
> Failed to retrieve unit state: Transport endpoint is not connected
> ssh.service is a disabled or a static unit not running, not starting it.
> ^B^[[5~Reload daemon failed: Transport endpoint is not connected
> Failed to get unit file state for ssh.socket: Transport endpoint is not connected
> Failed to retrieve unit state: Transport endpoint is not connected
> ...
> ```
> 
> And this process is very time-consuming also.

Hi,

This is all fairly clearly a systemd issue rather than anything
specifically to do with man-db, so reassigning there.  I'm afraid I
don't have any further clues though.

-- 
Colin Watson (he/him)                              [cjwatson at debian.org]