Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26022 - [systemd] Error messages at reboot or poweroff

Attached to Project: Community Packages
Opened by Daniel Gonzalez (maloy) - Thursday, 15 September 2011, 03:48 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 13 July 2013, 15:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Can't reboot or poweroff without this message:

Failed to get D-Bus connection: Failed to connect to
socket /org/freedesktop/systemd1/private: Connection refused

Steps to reproduce: Reboot or poweroff
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 13 July 2013, 15:32 GMT
Reason for closing:  None
Comment by Dave Reisner (falconindy) - Thursday, 15 September 2011, 11:10 GMT
You probably can't do a lot of other things, either. The error indicates that dbus isn't running and I'm really not sure what else to tell you based on the lack of information you've provided.
Comment by Daniel Gonzalez (maloy) - Thursday, 15 September 2011, 16:48 GMT
Sorry about the lack of information. It's weird, I have no problem with D-bus, it seems to be running as normal, but I'm always get that message at reboot:

Failed to get D-Bus connection: Failed to connect to
socket /org/freedesktop/systemd1/private: Connection refused

I've already added the and dbus.service to systemd (I'm not using the rc.conf daemons; the message appear too with rc.conf), everything works with no problem. According to systemd, dbus it's running:

# systemctl status dbus.service
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Thu, 15 Sep 2011 10:04:07 -0600; 4min 33s ago
Process: 1865 ExecStartPre=/bin/rm -f /var/run/dbus.pid (code=exited, status=0/SUCCESS)
Process: 1857 ExecStartPre=/usr/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
Main PID: 1873 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
├ 1873 /usr/bin/dbus-daemon --system --address=systemd: -...
├ 1895 /usr/lib/polkit-1/polkitd
├ 2077 /usr/lib/upower/upowerd
├ 2234 /usr/lib/udisks/udisks-daemon
└ 2236 udisks-daemon: polling /dev/sr0

I think it can be related to this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635757
   messages.log (276.8 KiB)
Comment by Dave Reisner (falconindy) - Thursday, 15 September 2011, 16:56 GMT
Highly unlikely there's any correlation. systemd 29 is referenced in the Debian bug report.

From your log:
Sep 15 10:29:44 localhost systemd[1]: /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output.

Please fix this.

You also have yet to mention _how_ you're getting this error. What command(s) are you running?
Comment by Dave Reisner (falconindy) - Thursday, 15 September 2011, 17:52 GMT
Also from your log...

1520 Sep 15 10:33:27 localhost shutdown[2140]: shutting down for system halt
1521 Sep 15 10:33:27 localhost systemd-initctl[2142]: Received environment initctl request. This is not implemented in systemd.
Comment by Daniel Gonzalez (maloy) - Thursday, 15 September 2011, 19:39 GMT
I forget to symlink the /etc/mtab, I'm in a fresh install. Now it's done.

The error appears everytime that I restart (and shutdown) the system. I'm just doing it from the gnome-panel menu or applet.

New log.
   messages.log (1.59 MiB)
Comment by Dave Reisner (falconindy) - Thursday, 15 September 2011, 19:51 GMT
This sounds more like a problem with gnome than with systemd... does something like 'sudo systemctl poweroff' or 'sudo systemctl reboot' work?
Comment by Daniel Gonzalez (maloy) - Thursday, 15 September 2011, 20:17 GMT
I've running # systemctl poweroff and # systemctl reboot. No luck.

Can it be related to D-bus, as in the Debian bug report? D-bus (in Debian Sid) it's 1.4.14, as in Arch.

Comment by Dave Reisner (falconindy) - Thursday, 15 September 2011, 20:28 GMT
The debian bug report shows that the user is running dbus from the devel branch -- the 1.5 series.

I suggest you enable debug logging -- raise the level in /etc/systemd/system.conf and ensure that debug level messages are rerouted by your syslogger to a file. I'm not really sure what's happening here as I can't reproduce it and nothing really stands out.

Please also provide versions for the following packages:

systemd
udev
dbus-core
dbus
Comment by Daniel Gonzalez (maloy) - Thursday, 15 September 2011, 20:43 GMT
systemd 35-1
udev 173-3
dbus-core 1.4.14-1
dbus 1.4.14-1
Comment by Dave Reisner (falconindy) - Monday, 28 November 2011, 01:32 GMT
Is this still a problem?
Comment by wry (wry) - Saturday, 13 July 2013, 09:30 GMT
  • Field changed: Percent Complete (100% → 0%)
My computer is exhibiting this behavior as well.
Comment by Dave Reisner (falconindy) - Saturday, 13 July 2013, 15:32 GMT
You reopened an 18-month old bug to post a "me too"? You're probably seeing this:

https://bbs.archlinux.org/viewtopic.php?id=162905

It's "fixed" upstream.

Loading...