Bug 1985126 - Failed to get properties: Connection timed out
Summary: Failed to get properties: Connection timed out
Keywords:
Status: CLOSED DUPLICATE of bug 1984651
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-22 23:20 UTC by Craig T
Modified: 2021-07-23 11:15 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-23 11:15:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Craig T 2021-07-22 23:20:40 UTC
Description of problem:
Performing various system actions results in timeout messages

[root@fedora ~]# systemctl status systemd-oomd
Failed to get properties: Connection timed out

[root@fedora ~]# rpm-ostree status
error: Timeout was reached

[root@fedora ~]# reboot
Failed to open initctl fifo: No such device or address
Failed to talk to init daemon.


Version-Release number of selected component (if applicable):

Version: 34.20210720.0 (2021-07-20T09:32:52Z)

[root@fedora ~]# uname -r
5.12.17-300.fc34.x86_64

[root@fedora ~]# rpm-ostree status
State: idle
Deployments:
  ostree://fedora-iot:fedora/stable/x86_64/iot
                   Version: 34.20210720.0 (2021-07-20T09:32:52Z) <- impacted
                BaseCommit: ed30314058e885603a3b66e6ed591736e496c0044fe87cc8b5b30c4c59be7687
              GPGSignature: Valid signature by 8C5BA6990BDB26E19F2A1A801161AE6945719A39
                      Diff: 144 upgraded, 1 added
           LayeredPackages: catatonit cockpit-ostree cockpit-podman cockpit-system git

* ostree://fedora-iot:a023dc06e52d0537c28bf8882bd229abf89cf7976dd16e9e2988348e6db23b2d
                   Version: 34.20210519.0 (2021-05-19T15:13:18Z) <- not impacted
                BaseCommit: a023dc06e52d0537c28bf8882bd229abf89cf7976dd16e9e2988348e6db23b2d
              GPGSignature: Valid signature by 8C5BA6990BDB26E19F2A1A801161AE6945719A39
           LayeredPackages: catatonit cockpit-ostree cockpit-podman cockpit-system git




How reproducible:


Steps to Reproduce:
1. When running 34.20210720.0, execute system related commands shown above example

Actual results:
1. Commands timeout

Expected results:
2. Commands should work

Additional info:

On boot the below systemd logs are seen in journal
>
Jul 22 18:54:09 fedora systemd-oomd[792]: Event loop failed: Connection refused
Jul 22 18:54:09 fedora systemd-oomd[792]: Failed to acquire varlink connection: Connection refused
Jul 22 18:54:09 fedora systemd-oomd[792]: Failed to connect to /run/systemd/io.system.ManagedOOM: Connection refused
Jul 22 18:54:09 fedora systemd[1]: Freezing execution.
Jul 22 18:54:09 fedora systemd[1]: Caught <ABRT>, dumped core as pid 8125.
Jul 22 18:54:09 fedora systemd-coredump[8126]: [🡕] Process 8125 (systemd) of user 0 dumped core.

                                               Stack trace of thread 8125:
                                               #0  0x00007f36508a859b kill (libc.so.6 + 0x3d59b)
                                               #1  0x000056488e897bc8 crash (systemd + 0x45bc8)
                                               #2  0x00007f3650a4da20 __restore_rt (libpthread.so.0 + 0x13a20)
                                               #3  0x00007f36508a82a2 raise (libc.so.6 + 0x3d2a2)
                                               #4  0x00007f36508918a4 abort (libc.so.6 + 0x268a4)
                                               #5  0x00007f3650beaa42 log_assert_failed.cold (libsystemd-shared-248.so + 0x78a42)
                                               #6  0x00007f3650d83dcf sleep_between (libsystemd-shared-248.so + 0x211dcf)
                                               #7  0x00007f3650d8c319 event_arm_timer (libsystemd-shared-248.so + 0x21a319)
                                               #8  0x00007f3650d8cd55 sd_event_prepare (libsystemd-shared-248.so + 0x21ad55)
                                               #9  0x00007f3650d8fdb0 sd_event_run (libsystemd-shared-248.so + 0x21ddb0)
                                               #10 0x000056488e8dc7d4 manager_loop (systemd + 0x8a7d4)
                                               #11 0x000056488e894c5f main (systemd + 0x42c5f)
                                               #12 0x00007f3650892b75 __libc_start_main (libc.so.6 + 0x27b75)
                                               #13 0x000056488e89777e _start (systemd + 0x4577e)
Jul 22 18:54:09 fedora systemd-coredump[8126]: Due to PID 1 having crashed coredump collection will now be turned off.
Jul 22 18:54:09 fedora audit[8126]: AVC avc:  denied  { write } for  pid=8126 comm="systemd-coredum" name="core_pattern" dev="proc" ino=15685 scontext=system_u:system_r:systemd_coredump_t:s0 tcontext=system_u:object_r:usermodehelper_>
Jul 22 18:54:08 fedora systemd[1]: Assertion 'a <= b' failed at src/libsystemd/sd-event/sd-event.c:2903, function sleep_between(). Aborting.
Jul 22 18:54:08 fedora audit[8125]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:init_t:s0 pid=8125 comm="systemd" exe="/usr/lib/systemd/systemd" sig=6 res=1
Jul 22 18:54:06 fedora systemd[1]: Failed to start Podman container-cockpit-ws.service.

Comment 1 Craig T 2021-07-22 23:22:51 UTC
Although it's shown above I forgot to mention this is on Fedora iot

Comment 2 bengt 2021-07-23 10:24:53 UTC
I have same experience on several Fedora install.

kernel-core-5.13.4-200.fc34.x86_64
kernel-modules-5.13.4-200.fc34.x86_64
kernel-5.13.4-200.fc34.x86_64
systemd-rpm-macros-248.5-1.fc34.noarch
systemd-libs-248.5-1.fc34.x86_64
systemd-networkd-248.5-1.fc34.x86_64
systemd-pam-248.5-1.fc34.x86_64
systemd-udev-248.5-1.fc34.x86_64
systemd-oomd-defaults-248.5-1.fc34.x86_64
systemd-248.5-1.fc34.x86_64

Comment 3 Zbigniew Jędrzejewski-Szmek 2021-07-23 11:15:16 UTC
This is caused by PID1 crashing on a failed assertion.

*** This bug has been marked as a duplicate of bug 1984651 ***


Note You need to log in before you can comment on or make changes to this bug.