FS#39041 - DBUS systemd broken on new install

Attached to Project: Arch Linux
Opened by Johannes Jordan (FoPref) - Tuesday, 25 February 2014, 15:54 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 25 February 2014, 16:10 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
On startup, systemd puts out the error message:
Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
This error message is repeated when calling systemctl restart dbus.

Further down the road this means that systemd-logind fails, org.freedesktop.systemd1 fails, there are huge timeouts during login. A login on the console takes 2 minutes, a login within KDM takes much longer, the user thinks she is unable to login!

The problem is that dbus does not create its bus socket in /var/run/dbus, but in /run/dbus!
A symlink ln -s /run/dbus /var/run/dbus solves the problem.

Additional info:
* all packages up-to-date, installed this morning then did full system update

* systemctl status dbus.socket dbus.service
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Tue 2014-02-25 16:40:46 CET; 11min ago
Listen: /run/dbus/system_bus_socket (Stream)

Feb 25 16:40:46 lme132 systemd[1]: Starting D-Bus System Message Bus Socket.
Feb 25 16:40:46 lme132 systemd[1]: Listening on D-Bus System Message Bus Socket.

dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2014-02-25 16:40:46 CET; 11min ago
Main PID: 229 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─229 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation


Steps to reproduce:
- Fresh install
- Run systemctl restart dbus
- See journalctl, etc.
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 25 February 2014, 16:10 GMT
Reason for closing:  Not a bug
Additional comments about closing:  user error. /var/run is a symlink to /run.
Comment by Dave Reisner (falconindy) - Tuesday, 25 February 2014, 16:04 GMT
> A symlink ln -s /run/dbus /var/run/dbus solves the problem.
/var/run is a symlink to /run. Not sure what you've broken here.
Comment by Doug Newgard (Scimmia) - Tuesday, 25 February 2014, 16:09 GMT
/var/run is a symlink to ../run, so /var/run/dbus and /run/dbus are the same thing. That symlink is owned by the filesystem package, do you not have that?

Under additional info, please don't just say "all packages up-to-date". This becomes meaningless very quickly in a fast paced rolling release, and is meaningless from the start when we have multiple versions of a package in the repos, like now with systemd 208 in [core] and systemd 210 in [testing].
Comment by Johannes Jordan (FoPref) - Tuesday, 25 February 2014, 16:09 GMT
On some occasion I did mkdir -p /var/run/nscd
It was a bad idea!
Sorry for that.

Loading...