I did and it is now okay, even after a restart.
Thanks !
As of filesystem-2012.6-2 the folders /var/run and /var/lock will be replaced by symlinks to /run and /run/lock, respectively.
So yes, I would delete /var/{run,lock} and replace them with symlinks (if there is anything in them already, move it to /run and /run/lock respectively).
And I've no idea why it occurred, sorry!
Happy new year to you too,
]]>Happy new year, by the way !
Nope exactly the same :
[root@zoulou dbus]# ls -ld /var/run/ /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /var/run/
[root@zoulou dbus]# pacman-color -S filesystem
warning: filesystem-2012.12-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
.
.
.
[root@zoulou dbus]# ls -ld /var/run/ /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /var/run/
[root@zoulou dbus]#
Strange. I can create the simlink by myself, but :
- first, I do not get any error so should I change something if everything is right ?
- second, I would like to understand why the problem occured...
Regards and happy new year again,
Bastien
[root@zoulou run]# pwd
/var/run
[root@zoulou run]# ls
[root@zoulou run]# cd /run/dbus/
[root@zoulou dbus]#
It sounds like you had the same problem as I did: /var/run wasn't symlinked to /run. Run
ls -ld /var/run /run
to check and you should get something like
drwxr-xr-x 21 root root 520 Jan 1 10:05 /run
lrwxrwxrwx 1 root root 6 Dec 4 01:02 /var/run -> ../run
Regards,
]]>Everything is okay now.
Why on Earth this problem sudendly occured ?
I have done :
[root@zoulou bastien]# pacman-color -S filesystem
warning: filesystem-2012.12-1 is up to date -- reinstalling
Now I have :
[root@zoulou run]# cd /var/run
[root@zoulou run]# ls
console dbus initramfs lirc lock log lvm mdadm mount network nscd pm-utils syslog-ng.ctl syslog-ng.pid systemd udev user utmp uuidd
[root@zoulou run]#
And the log file :
Jan 1 00:51:38 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Jan 1 00:51:38 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jan 1 00:51:38 zoulou systemd[1]: Stopping Login Service...
Jan 1 00:51:38 zoulou systemd[1]: Starting Login Service...
Jan 1 00:51:38 zoulou systemd[1]: Starting D-Bus System Message Bus...
Jan 1 00:51:38 zoulou systemd[1]: Started D-Bus System Message Bus.
Jan 1 00:51:38 zoulou systemd[1]: Started Login Service.
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Jan 1 00:51:40 zoulou systemd[1]: Starting Daemon for power management...
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Successfully activated service 'org.freedesktop.UPower'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Successfully activated service 'org.freedesktop.UPower'
Jan 1 00:51:40 zoulou systemd[1]: Started Daemon for power management.
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 1 00:51:40 zoulou systemd[1]: Starting Authorization Manager...
Jan 1 00:51:40 zoulou polkitd[2938]: Started polkitd version 0.107
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 1 00:51:40 zoulou systemd[1]: Started Authorization Manager.
Jan 1 00:51:40 zoulou kernel: [ 2815.729436] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.732372] EXT4-fs (sda1): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.733673] EXT4-fs (dm-1): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.735586] EXT4-fs (dm-3): re-mounted. Opts: stripe=256,data=ordered,commit=0
I have the same problem.
[root@zoulou run]# pwd
/var/run
[root@zoulou run]# ls
[root@zoulou run]# cd /run/dbus/
[root@zoulou dbus]# ls
system_bus_socket
[root@zoulou dbus]# ls -lha
total 0
drwxr-xr-x 2 root root 60 Jan 1 00:04 .
drwxr-xr-x 17 root root 400 Jan 1 00:04 ..
srw-rw-rw- 1 root root 0 Jan 1 00:04 system_bus_socket
[root@zoulou dbus]# file system_bus_socket
system_bus_socket: socket
[root@zoulou dbus]#
But I have installed Arch let's say... two months ago so I have a complete-full systemd "compliant OS.
It was working fine until this evening, I was just googling and reading newspaper and sudenly Conky display a log of messages from /var/log/messages.log !
My Arch is up to date.
I have tried to restart a couple of time but nothing change.
Do you have an idea ?
Dec 31 21:10:20 zoulou dbus-daemon[945]: dbus[945]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:20 zoulou dbus[945]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:45 zoulou dbus-daemon[945]: dbus[945]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:10:45 zoulou dbus[945]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:10:45 zoulou dbus[945]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:10:45 zoulou dbus-daemon[945]: dbus[945]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:10:45 zoulou dbus-daemon[945]: process 945: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
Dec 31 21:10:45 zoulou dbus-daemon[945]: This is normally a bug in some application using the D-Bus library.
Dec 31 21:10:45 zoulou dbus-daemon[945]: D-Bus not built with -rdynamic so unable to print a backtrace
Dec 31 21:10:45 zoulou systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Dec 31 21:10:45 zoulou systemd[1]: Unit dbus.service entered failed state
Dec 31 21:10:45 zoulou systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Dec 31 21:10:45 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Dec 31 21:10:45 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 31 21:10:45 zoulou systemd[1]: Stopping Login Service...
Dec 31 21:10:45 zoulou systemd[1]: Starting Login Service...
Dec 31 21:10:45 zoulou systemd[1]: Starting D-Bus System Message Bus...
Dec 31 21:10:45 zoulou systemd[1]: Started D-Bus System Message Bus.
Dec 31 21:10:45 zoulou systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Dec 31 21:10:47 zoulou dbus-daemon[954]: dbus[954]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:47 zoulou dbus[954]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:11:12 zoulou dbus-daemon[954]: dbus[954]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:11:12 zoulou dbus[954]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:11:12 zoulou dbus[954]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:11:12 zoulou dbus-daemon[954]: dbus[954]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:11:12 zoulou dbus-daemon[954]: process 954: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
Dec 31 21:11:12 zoulou dbus-daemon[954]: This is normally a bug in some application using the D-Bus library.
Dec 31 21:11:12 zoulou dbus-daemon[954]: D-Bus not built with -rdynamic so unable to print a backtrace
Dec 31 21:11:12 zoulou systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Dec 31 21:11:12 zoulou systemd[1]: Unit dbus.service entered failed state
Dec 31 21:11:12 zoulou systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Dec 31 21:11:12 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Dec 31 21:11:12 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
[root@zoulou dbus]#
I've rectified the situation, and polkitd starts correctly. I'll reboot now and see if the problem's fixed...
]]>There's your problem. (Well, one of them, anyway.)
/var/run should be a symlink to /run.
If that is not the case on your machine, either your system is rather out of date or something has gone rather wrong somewhere.
]]>[joshua:~ o]$ sudo systemctl list-units --no-pager | grep dbus
zsh: correct 'dbus' to '.dbus' [nyae]? n
dbus.service loaded active running D-Bus System Message Bus
dbus.socket loaded active running D-Bus System Message Bus Socket
[joshua:~ o]$ diff -u {/etc/skel/,}.xinitrc
--- /etc/skel/.xinitrc 2011-03-10 19:03:55.000000000 +0000
+++ .xinitrc 2012-09-29 15:28:27.425170931 +0100
@@ -11,7 +11,23 @@
unset f
fi
-# exec gnome-session
-# exec startkde
-# exec startxfce4
-# ...or the Window Manager of your choice
+trayer --edge top --align left --SetDockType true --SetPartialStrut true --expand true --widthtype pixel --width 101 --transparent true --tint 0x002b36 --height 12 --margin 922 &
+xautolock -time 30 -locker "sudo pm-suspend" & #suspends to RAM after 30 mins of inactivity
+
+setxkbmap -option compose:ralt
+setxkbmap -option terminate:ctrl_alt_bksp
+xmodmap -e "keysym Num_Lock = Num_Lock Pointer_EnableKeys"
+xhost local:boinc # allows boinc to use GPU for calculations
+xsetroot -solid "#002b36"
+xrdb -merge ~/.Xresources
+
+xscreensaver -no-splash &
+conky &
+dropbox start &
+
+(logtime "START anki"; anki) &
+urxvt -e sh -c "sudo pacman -Syu; echo -e \"\nFinished.\"; read; weather; read; tdl list; read; sudo backup daily; read" &
+
+#(sleep 120; transmission-gtk) &
+
+exec xmonad
[joshua:~ x]$
I haven't,, but as you can see I have nothing the /etc/skel/.xinitrc doesn't have...
I also tried swapping the last line for
dbus-launch --exit-with-session xmonad
but to no avail (exactly the same symptoms when trying to start polkitd manually, or trying to systemctl poweroff without root priveliges).
]]># systemctl list-units
to check the status of dbus. Did you try and copy /etc/skel/.xinitrc to your home directory like I suggested before? It looks like dbus isn't running or responding properly for some reason. I think I read somewhere that someone was still using dbus-launch in his .xinitrc and it worked for him.
As far as groups are concerned the systemd wiki claims you don't need to be in groups in most cases.
]]>DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket
doesn't help at all.
Also, I note that in /etc/dbus-1/system.conf has
<listen>unix:path=/run/dbus/system_bus_socket</listen>
in it.
Any ideas?
]]>I have /usr/lib/systemd/system/dbus.socket but according to "locate", no files named "system-bus-socket" in the filesystem ( also ran "find /var -iname 'system-bus-socket'" just in case, but no luck there either).
I found http://lists.freedesktop.org/archives/d … 09206.html: I don't have messagebus user/group, but I do have dbus user/group. Is this the source of my problem, do you think?
[EDIT]Nope, I added a messagebus user and group and the problem persists...[/EDIT]
]]>