Bug 634765 - Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused
Summary: Failed to connect to socket /org/freedesktop/systemd1/private: Connection ref...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-16 23:17 UTC by Piavlo
Modified: 2011-07-18 20:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-18 20:38:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Piavlo 2010-09-16 23:17:34 UTC
Description of problem:

[root@fedora2 ~]# systemctl
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused
[root@fedora2 ~]# rpm -qa | grep fedora

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

systemd-10

How reproducible:

after upgrade from systemd-9 to systemd-10 and reboot

Comment 1 Michal Schmidt 2010-09-17 06:46:50 UTC
Please verify that you have booted with systemd, using "readlink /proc/1/exe". 

Fedora 14 has switched back to upstart by default. Which one is the default depends on whether you have upstart-sysvinit or systemd-sysvinit installed.

Comment 2 Piavlo 2010-09-17 22:09:08 UTC
(In reply to comment #1)
> Please verify that you have booted with systemd, using "readlink /proc/1/exe". 
> 
it's upstart indeed 

> Fedora 14 has switched back to upstart by default. Which one is the default
> depends on whether you have upstart-sysvinit or systemd-sysvinit installed.

trying to install systemd-sysvinit  yum says:
Package systemd-sysvinit is obsoleted by upstart-sysvinit, trying to install upstart-sysvinit-0.6.5-8.fc14.x86_64 instead

So how do I tell in the bootlader to boot with systemd?
and how do i install the systemd-sysvinit?

Thanks
Alex

Comment 3 Piavlo 2010-09-17 22:40:39 UTC
(In reply to comment #2)
> So how do I tell in the bootlader to boot with systemd?

ok i managed with init=/bin/systemd

> and how do i install the systemd-sysvinit?

Comment 4 Matthias Clasen 2010-10-08 22:46:27 UTC
Moving systemd bugs to f15, since the systemd feature got delayed.

Comment 5 Lennart Poettering 2010-11-18 23:25:23 UTC
I think this bug is fixed for F15 now, since we do not support optional upstart booting anymore.

Comment 6 Pavel Zhukov 2011-06-21 07:33:10 UTC
# systemctl -f reboot 
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

# rpm -q systemd
systemd-26-3.fc15.x86_64


Checked on 2 systems with minimal installation.

Comment 7 Pavel Zhukov 2011-06-21 09:01:44 UTC
[root@kartman xorg.conf.d]# /etc/init.d/messagebus start
Starting messagebus (via systemctl):  Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused
                                                           [FAILED]

Comment 8 Michal Schmidt 2011-06-21 09:28:32 UTC
Pavel,
What does "readlink /proc/1/exe" show on your system?

> Checked on 2 systems with minimal installation.

So does this happen immediately on the first boot after a fresh minimal installation?

Comment 9 Pavel Zhukov 2011-06-21 09:50:46 UTC
# readlink /proc/1/exe
/bin/systemd

I didn't check it after first boot. It happened after Xorg and xmonad installations (keyboard and mouse don't work).

Comment 10 Michal Schmidt 2011-06-21 10:03:27 UTC
Please boot with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg" and attach the output of 'dmesg'.

Comment 11 Pavel Zhukov 2011-06-21 10:34:27 UTC
Done:
http://fpaste.org/xtdp/

Comment 12 Michal Schmidt 2011-06-21 21:33:22 UTC
I don't see any problems with D-Bus indicated in the log.

What does this command show?: ls -l /run/systemd/private

There is one oddity:
 [    1.243555] dracut: dracut-009-11.fc15.1.R
This is not a Fedora version of the package. It must have been modified. How?
I wonder what else is modified.

Comment 13 Pavel Zhukov 2011-06-22 03:52:33 UTC
(In reply to comment #12)
> I don't see any problems with D-Bus indicated in the log.

I see one problem. D-Bus doesn't work :) 

> There is one oddity:
>  [    1.243555] dracut: dracut-009-11.fc15.1.R
> This is not a Fedora version of the package. It must have been modified. How?
> I wonder what else is modified.

This is modification from RFRemix with Russian fonts fix
http://mirror.yandex.ru/fedora/russianfedora/russianfedora/fixes/fedora/releases/15/Everything/source/SRPMS/dracut-009-10.fc15.1.R.src.rpm

Changelog: 
* Fri May 13 2011 Arkady L. Shane <ashejn> 009-10.1.R
- resolved incomplete /run change for squashfs
Resolves: rhbz#699113

* Fri May 06 2011 Arkady L. Shane <ashejn> 009-9.1.R
- fixed console font loading (working fix of rhbz#700971)

Comment 14 Pavel Zhukov 2011-06-22 05:18:21 UTC
ls: cannot access /run/systemd/private: No such file or directory

Comment 15 Pavel Zhukov 2011-06-22 05:30:13 UTC
with upstream version of dracut:
# rpm -q dracut
dracut-009-10.fc15.noarch
# /etc/init.d/messagebus status
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

and debug dmesg after "reboot"
http://fpaste.org/pfut/

Comment 16 Michal Schmidt 2011-06-22 07:19:03 UTC
(In reply to comment #14)
> ls: cannot access /run/systemd/private: No such file or directory

Does /run exist? Does /run/systemd exist?
Please attach the output of 'findmnt'.

Comment 17 Lennart Poettering 2011-06-22 18:02:32 UTC
Hmm, usually, if /run/systemd/private is not connectable systemd crashed.

Could you attach a gdb to PID 1 and get a backtrace? "gdb /bin/systemd 1" and then "bt full". But please run "debuginfo-install systemd" first, to install the debugging symbols.

Comment 18 Pavel Zhukov 2011-07-18 20:38:53 UTC
I've reinstalled system. So I cannot reproduce this again.


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