Wednesday, October 26, 2011

Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Problem:
X windows does not start on runlevel 5.

In RedHat RHEL 6.1, you get this message in system log (in /var/log/messages, by default):
Oct 26 15:41:15 testserver1 kernel: readahead-collector: sorting
Oct 26 15:41:15 testserver1 kernel: readahead-collector: finished
Oct 26 15:54:05 testserver1 abrtd: Error requesting DBus name com.redhat.abrt, possible reasons: abrt run by non-root; dbus config is incorrect; or dbus daemon needs to be restarted to reload dbus config
Oct 26 15:54:06 testserver1 init: start-ttys main process (4086) terminated with status 1
Oct 26 15:55:20 testserver1 ck-xinit-session: error connecting to console-kit
Oct 26 15:55:21 testserver1 gnome-session[4164]: devkit-power-gobject-WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Oct 26 15:55:21 testserver1 gnome-session[4164]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Oct 26 15:55:21 testserver1 gnome-session[4164]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Oct 26 15:55:22 testserver1 kernel: fuse init (API version 7.13)
Oct 26 15:55:22 testserver1 pulseaudio[4213]: core-util.c: Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Oct 26 15:55:22 testserver1 pulseaudio[4213]: core-util.c: Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory


Solution:
Check if messagebus service is turned on:
chkconfig --list messagebus

If messagebus is turned off, turn it on:
chkconfig messagebus on

Now it should look something like this:
chkconfig --list messagebus
messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off

Then just reboot your server:
shutdown -r now


Reference:
http://fixunix.com/mandriva/397862-dbus-error.html

4 comments:

  1. I have always tried to live by the philosophy that when there is a big problem that needs fixing, you should run towards it, rather than away from it. See the link below for more info.


    #fixing
    www.ufgop.org



    ReplyDelete
  2. We are all like flowers that blooms or withered in the garden depending on how we take good care of our self. So do not let negativity pass through. Enjoy and be confident. Have a good day and visit my site for more information.

    n8fan.net

    www.n8fan.net

    ReplyDelete
  3. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 3 07:41:15 2016
    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    error setting MTRR (base = 0xfc000000, size = 0x00100000, type = 1) Invalid argu ment (22)
    gnome-session[1835]: WARNING: Could not connect to ConsoleKit: Could not get own er of name 'org.freedesktop.ConsoleKit': no such name
    gnome-session[1835]: WARNING: Could not connect to ConsoleKit: Could not get own er of name 'org.freedesktop.ConsoleKit': no such name
    GNOME_KEYRING_SOCKET=/tmp/keyring-uT8wQc/socket
    SSH_AUTH_SOCK=/tmp/keyring-uT8wQc/socket.ssh
    GNOME_KEYRING_PID=1867

    ** (gnome-panel:1887): WARNING **: panel-applet-frame.c:1288: failed to load app let OAFIID:GnoteApplet:
    (null)

    ReplyDelete
  4. Aw, this was a very nice post. In concept I want to put in writing like this additionally – taking time and actual effort to make an excellent article… but what can I say… I procrastinate alot and certainly not appear to get one thing done. bovada casino

    ReplyDelete