I am experiencing serious problems with systemd & dbus.
I want to setup a gateway in a KVM VM, all was working fine till i applied my shorewall config & set to autostart (systemctl enable shorewall).
If I reboot the machine after this step one or two times, then I get a broken dbus service.
What I did than: reinstalled archlinux again (x86_x64) and setup same -> got issue again.
installed arch linux as x86 and setup same -> issue again
installed arch as x86 and configured nothing else shorewall and got this issue again after maximum of two reboots.
i found in log:
Feb 13 15:45:56 pactor systemd: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I've checked this directory by hand and found that only /var/run is existing. /var/run/dbus is already not existing.
journalctl -b: http://nopaste.info/685f4c6192.html
-be aware of systemd-logind, this needs dbus and i experience same problem with other services which require dbus as dnsmasq
root@pactor ~]# systemctl status dbus dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago Main PID: 169 (dbus-daemon) CGroup: name=systemd:/system/dbus.service └─169 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation [root@pactor ~]# systemctl status dbus.socket dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static) Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago Feb 13 15:45:56 pactor systemd: Listening on D-Bus System Message Bus Socket. systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Active: activating (start) since Mi 2013-02-13 16:00:56 CET; 48s ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 338 (systemd-logind) CGroup: name=systemd:/system/systemd-logind.service └─338 /usr/lib/systemd/systemd-logind Feb 13 16:00:56 pactor systemd: Failed to start Login Service. Feb 13 16:00:56 pactor systemd: Unit systemd-logind.service entered failed state Feb 13 16:00:56 pactor systemd: systemd-logind.service holdoff time over, scheduling restart. Feb 13 16:00:56 pactor systemd: Stopping Login Service... Feb 13 16:00:56 pactor systemd: Starting Login Service...
Last edited by debijan (2013-02-20 20:13:47)
oh man... found the reason due to help of some guys on systemd irc... big thx to falconindy and alxchk.
shorewall's SUBSYSLOCK option in shorewall.conf is by default set to /var/lock/shorewall.
but the arch wiki point that it should be set to /var/run: https://wiki.archlinux.org/index.php/Router
definitely wrong! that deletes the /var/run symlink and created a directory intstead.
to set the SUBSYSLOCK on default is working like a charm.
look also for this: https://bbs.archlinux.org/viewtopic.php?id=151285
could somebody modify the wiki in the meantime, i will hold this thread on -not-solved in the meantime
edit:/ oh man this wrong info in wiki did cost me a lot of time :-/
Last edited by debijan (2013-02-13 22:09:35)
@debijan: How about modifying the wiki by yourself? The wiki is a community project.
To know or not to know ...
... the questions remain forever.
fixed wiki now :-)