Bug 1937504 - On "reboot": "Failed to open initctl fifo: No such device or address"
Summary: On "reboot": "Failed to open initctl fifo: No such device or address"
Keywords:
Status: CLOSED DUPLICATE of bug 1931034
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-03-10 19:12 UTC by Hans Ulrich Niedermann
Modified: 2021-03-12 14:05 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-03-12 14:05:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hans Ulrich Niedermann 2021-03-10 19:12:14 UTC
Description of problem:

  As root, type "reboot" in a shell. Nothing happens for a number of seconds.
  Then the following two lines of error messages appear, and there is another
  shell prompt:

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

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

  systemd-248~rc2-3.fc34.x86_64

How reproducible:

  Occasionally. I have not found a reproducible way to get the system into
  this state.

Steps to Reproduce:

  This describes the last time this happened. I have also seen the messages
  about the initctl file missing a week or two ago, but I cannot remember
  the things I did back then, or what version of systemd was installed back
  then.

    1. Use F34 in Gnome with or without X.
    2. suspend-to-ram ("echo mem > /sys/power/state") a few times over a few days
    3. some time after the resume, the screens remain black, no reaction to
       keyboard/mouse, and ssh access only allows rebooting with
       "systemctl --force --force reboot"

Actual results:

  System does not react to keyboard input, screens stay black with a mouse
  pointer, and the system requires a special reboot command or a hardware
  reset to reboot.

Expected results:

  System continues working after resume from STR.

Additional info:

  I cannot tell what this is may related to, or even how to reproduce it.
  It just happens to happen from time to time.

Comment 1 Zbigniew Jędrzejewski-Szmek 2021-03-12 14:05:08 UTC
Oh, this is probably the same as 1931034. Please reopen if the issue occurs again with
systemd-248~rc2-5.fc34 or newer.

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


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