You are not logged in.

Pages: 1

#1 2025-01-19 12:55:44

farben.rausch
Member
Registered: 2011-10-25
Posts: 21

Failed t. con. to sys. scope bus via local transp.: Connection refused

I am trying to debug this message
"Failed to connect to system scope bus via local transport: Connection refused"

The internet is basically empty regarding it and I have no clue how to receive any help.
Seemingly similar is this recent forum post but I am not convinced that it is the same.

The problem:

# systemctl list-units
Failed to connect to system scope bus via local transport: Connection refused

The same also happens during the update process...

:: Running post-transaction hooks...
(1/8) Creating system user accounts...
(2/8) Reloading system manager configuration...
Failed to connect to system scope bus via local transport: Connection refused
error: command failed to execute correctly
(3/8) Restarting marked services...
Failed to connect to system scope bus via local transport: Connection refused
error: command failed to execute correctly
(4/8) Creating temporary files...
(5/8) Reloading device manager configuration...
(6/8) Arming ConditionNeedsUpdate...
(7/8) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.12.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.12.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(8/8) Reloading system bus configuration...
Failed to connect to system scope bus via local transport: Connection refused
error: command failed to execute correctly

reboot tricky (same with shutdown -r now):

# reboot                                                                                                                                    

Broadcast message from root@garten on pts/1 (Sun 2025-01-19 14:02:51 CET):

The system will reboot now!

Call to Reboot failed: Connection timed out
Failed to connect to system scope bus via local transport: Connection refused
Failed to talk to init daemon: Connection refused

-> reboot --force --force did the trick

Additional symptoms:
Logging in and using sudo command take nearly a minute!

I can in theory drive to the server location and hard reboot it but I prefer debugging a bit more before that.
Any ideas?

Last edited by farben.rausch (2025-01-19 16:21:39)

Offline

#2 2025-01-19 13:05:57

farben.rausch
Member
Registered: 2011-10-25
Posts: 21

Re: Failed t. con. to sys. scope bus via local transp.: Connection refused

journalctl --since today -u systemd-journald
reveals a many of those:

Jan 19 13:48:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:49:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:51:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:52:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:54:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:55:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:57:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 13:58:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:00:06 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:01:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:03:16 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:04:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:05:54 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:07:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:09:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:10:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:12:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:13:36 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Jan 19 14:15:04 garten systemd-journald[268]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

Offline

#3 2025-01-19 13:08:04

farben.rausch
Member
Registered: 2011-10-25
Posts: 21

Re: Failed t. con. to sys. scope bus via local transp.: Connection refused

journalctl --since today -u systemd-logind

Jan 19 01:15:31 garten systemd-logind[411]: Failed to remove file descriptor "session-95444-leader-fd" from the store, ignoring: Connection refused
Jan 19 01:15:31 garten systemd-logind[411]: Failed to push leader pidfd for session '95444', ignoring: Connection refused
Jan 19 01:15:56 garten systemd-logind[411]: Failed to start session scope session-95444.scope: Connection timed out
Jan 19 01:15:56 garten systemd-logind[411]: Failed to remove file descriptor "session-95444-leader-fd" from the store, ignoring: Connection refused
Jan 19 02:14:39 garten systemd-logind[411]: Failed to remove file descriptor "session-95483-leader-fd" from the store, ignoring: Connection refused
Jan 19 02:14:39 garten systemd-logind[411]: Failed to push leader pidfd for session '95483', ignoring: Connection refused
Jan 19 02:15:04 garten systemd-logind[411]: Failed to start session scope session-95483.scope: Connection timed out
Jan 19 02:15:04 garten systemd-logind[411]: Failed to remove file descriptor "session-95483-leader-fd" from the store, ignoring: Connection refused
Jan 19 02:15:31 garten systemd-logind[411]: Failed to remove file descriptor "session-95484-leader-fd" from the store, ignoring: Connection refused
Jan 19 02:15:31 garten systemd-logind[411]: Failed to push leader pidfd for session '95484', ignoring: Connection refused
Jan 19 02:15:56 garten systemd-logind[411]: Failed to start session scope session-95484.scope: Connection timed out
Jan 19 02:15:56 garten systemd-logind[411]: Failed to remove file descriptor "session-95484-leader-fd" from the store, ignoring: Connection refused
Jan 19 03:14:39 garten systemd-logind[411]: Failed to remove file descriptor "session-95524-leader-fd" from the store, ignoring: Connection refused
Jan 19 03:14:39 garten systemd-logind[411]: Failed to push leader pidfd for session '95524', ignoring: Connection refused
Jan 19 03:15:04 garten systemd-logind[411]: Failed to start session scope session-95524.scope: Connection timed out
Jan 19 03:15:04 garten systemd-logind[411]: Failed to remove file descriptor "session-95524-leader-fd" from the store, ignoring: Connection refused
Jan 19 03:15:31 garten systemd-logind[411]: Failed to remove file descriptor "session-95525-leader-fd" from the store, ignoring: Connection refused
Jan 19 03:15:31 garten systemd-logind[411]: Failed to push leader pidfd for session '95525', ignoring: Connection refused
Jan 19 03:15:56 garten systemd-logind[411]: Failed to start session scope session-95525.scope: Connection timed out
Jan 19 03:15:56 garten systemd-logind[411]: Failed to remove file descriptor "session-95525-leader-fd" from the store, ignoring: Connection refused
Jan 19 04:14:39 garten systemd-logind[411]: Failed to remove file descriptor "session-95565-leader-fd" from the store, ignoring: Connection refused
Jan 19 04:14:39 garten systemd-logind[411]: Failed to push leader pidfd for session '95565', ignoring: Connection refused
Jan 19 04:15:04 garten systemd-logind[411]: Failed to start session scope session-95565.scope: Connection timed out
Jan 19 04:15:04 garten systemd-logind[411]: Failed to remove file descriptor "session-95565-leader-fd" from the store, ignoring: Connection refused
Jan 19 04:15:31 garten systemd-logind[411]: Failed to remove file descriptor "session-95566-leader-fd" from the store, ignoring: Connection refused
Jan 19 04:15:31 garten systemd-logind[411]: Failed to push leader pidfd for session '95566', ignoring: Connection refused
Jan 19 04:15:56 garten systemd-logind[411]: Failed to start session scope session-95566.scope: Connection timed out
Jan 19 04:15:56 garten systemd-logind[411]: Failed to remove file descriptor "session-95566-leader-fd" from the store, ignoring: Connection refused
Jan 19 05:14:39 garten systemd-logind[411]: Failed to remove file descriptor "session-95605-leader-fd" from the store, ignoring: Connection refused
Jan 19 05:14:39 garten systemd-logind[411]: Failed to push leader pidfd for session '95605', ignoring: Connection refused
Jan 19 05:15:04 garten systemd-logind[411]: Failed to start session scope session-95605.scope: Connection timed out
Jan 19 05:15:04 garten systemd-logind[411]: Failed to remove file descriptor "session-95605-leader-fd" from the store, ignoring: Connection refused
Jan 19 05:15:30 garten systemd-logind[411]: Failed to remove file descriptor "session-95606-leader-fd" from the store, ignoring: Connection refused
Jan 19 05:15:30 garten systemd-logind[411]: Failed to push leader pidfd for session '95606', ignoring: Connection refused
Jan 19 05:15:55 garten systemd-logind[411]: Failed to start session scope session-95606.scope: Connection timed out

Offline

#4 2025-01-19 16:16:37

seth
Member
Registered: 2012-09-03
Posts: 60,828

Re: Failed t. con. to sys. scope bus via local transp.: Connection refused

Just recording that you've found https://bbs.archlinux.org/viewtopic.php?id=302556 - you don't use n/vim?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2025-01-19 16:19:34

farben.rausch
Member
Registered: 2011-10-25
Posts: 21

Re: Failed t. con. to sys. scope bus via local transp.: Connection refused

seth wrote:

Just recording that you've found https://bbs.archlinux.org/viewtopic.php?id=302556 - you don't use n/vim?

I found that, I referred to this one in that thread.

I do use vim sometimes, e.g it is installed. Is that alone enough?

~ » pacman -Q vim                                                                                                                                                        
vim 9.1.1006-1

~ » pacman -Q systemd                                                                                                                                                    
systemd 257.2-2

Offline

#6 2025-01-19 17:31:31

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 23,923

Re: Failed t. con. to sys. scope bus via local transp.: Connection refused

you'd have to actively use it to try and view/modify systemd unit files, and standard vim shouldn't directly be affected if you haven't configured plugins/a LSP. My first guess was some broken DBUS config/xml? Or a wrong udev rule or so?

Offline

Pages: 1

Board footer

Powered by FluxBB