I cannot reproduce this anymore. Not sure under which circumstances it happened either, though I can distinctly recall that /dev/initctl existed and was a pipe. There was also nothing in the logs.

Frederik, assigning to you as you're listed as bugowner.

Might have been caused by systemd or udev being upgraded but I didn't got other reports. Let's close as work for me and reopen if somebody has the issue again.

Hello,

I'm having this same issue now. I'm upgrading from 12.3 to 13.1 release in an OpenVZ container, and not able to reboot the system after that

srv-db-us:~ # reboot
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

This remain exist after I downgrade back to 12.3.

I found that in ArchLinux community there's a thread about similiar problem https://bbs.archlinux.org/viewtopic.php?pid=1184306#p1184306 and it seems an old kernel is the problem. As I'm in an OpenVZ container, I have 2.6.32-042stab072.10 kernel and it's not likely to be upgraded.

reopen this bug

(In reply to comment #3)
> I found that in ArchLinux community there's a thread about similiar problem
> https://bbs.archlinux.org/viewtopic.php?pid=1184306#p1184306 and it seems an
> old kernel is the problem. As I'm in an OpenVZ container, I have
> 2.6.32-042stab072.10 kernel and it's not likely to be upgraded.

Ouch ... you can not use such an old kernel together with systemd

(In reply to comment #5)
> (In reply to comment #3)
> > I found that in ArchLinux community there's a thread about similiar problem
> > https://bbs.archlinux.org/viewtopic.php?pid=1184306#p1184306 and it seems an
> > old kernel is the problem. As I'm in an OpenVZ container, I have
> > 2.6.32-042stab072.10 kernel and it's not likely to be upgraded.
> 
> Ouch ... you can not use such an old kernel together with systemd

So... does this mean 13.1 no longer support running in OpenVZ anymore? (As I don't see any sign of OpenVZ to upgrade to 3.x kernel in near future)

(In reply to comment #6)

I don't know ... the only fact i know that systemd+udev depends heavily on the infrastructure below /sys and /proc ... and here is 2.6.32 != 3.11.6

From systemd-208/README

 REQUIREMENTS:
        Linux kernel >= 3.0
          CONFIG_DEVTMPFS
          CONFIG_CGROUPS (it's OK to disable all controllers)
          CONFIG_INOTIFY_USER
          CONFIG_SIGNALFD
          CONFIG_TIMERFD
          CONFIG_EPOLL
          CONFIG_NET
          CONFIG_SYSFS

        Linux kernel >= 3.8 for Smack support

I personally am fine to stick with 12.3 on the VPS, it works fine after downgrading from 13.1 to 12.3 and reboot from the contral panel. But I'd prefer any alternative way to run 13.1 inside the container as we can get newer packages with it.

I am seeing the same error message, but it is on physical hardware and using 13.1 GA with at least some patches.

# shutdown
Failed to talk to shutdownd, proceeding with immediate shutdown:
Connection refused
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon
#

I haven't tried the power switch yet.  I prefer not to.  I can
troubleshoot this for a day or two before I need to get that
desperate.

my wireless network is also offline, so it may be a different problem.  Let me know if I need to open a separate bug

== hardware

x86 laptop / Dell
32-bit kernel / system installed
3.11.6-4-desktop

== background

I don't recall apply "zypper patch" recently, but I might have and I certainly have a couple times since 13.1 was released.

Christian Rodríguez says it is a kernel regression. fixed in 3.11.8.  But this is the only openSUSE bugzilla I see that looks relevant.

Any suggestions welcome

Continuing research my issues, which may or may not be the same as this bug, I found this kernel bugzilla which lasted for a month of debugging.:

https://bugzilla.kernel.org/show_bug.cgi?id=61781

It concluded with this kernel patch that got pushed to 3.12 and I think to later 3.11.x kernels also.  Is this in the openSUSE 13.1 released kernel yet?

===========
diff --git a/fs/eventpoll.c b/fs/eventpoll.c
index 473e09d..810c28f 100644
--- a/fs/eventpoll.c
+++ b/fs/eventpoll.c
@@ -34,7 +34,6 @@
 #include <linux/mutex.h>
 #include <linux/anon_inodes.h>
 #include <linux/device.h>
-#include <linux/freezer.h>
 #include <asm/uaccess.h>
 #include <asm/io.h>
 #include <asm/mman.h>
@@ -1605,8 +1604,7 @@ fetch_events:
 			}
 
 			spin_unlock_irqrestore(&ep->lock, flags);
-			if (!freezable_schedule_hrtimeout_range(to, slack,
-								HRTIMER_MODE_ABS))
+			if (!schedule_hrtimeout_range(to, slack, HRTIMER_MODE_ABS))
 				timed_out = 1;
 
 			spin_lock_irqsave(&ep->lock, flags);

dup

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

This bug also happens on the installation system of openSUSE Leap 42.1 (ssh install). Yast was not able to do the first reboot and I also cannot reboot manually.

0:skylla.ga.local:~ # reboot
Failed to talk to init daemon.
0:skylla.ga.local:~ # uname -r
4.1.12-1-default

Are there updated installation systems available somewhere?

Leap 42.1 as well as 13.1 had already reached their End Of Live.  If this problem still exists with Tumbleweed or active Leap 42.3 then please reopen this bug to report this.