Mageia forum

Hi folks,

it seems my dbus installation is broken for some reason (not that it seems to be upsetting too much at the moment). I've noticed this for a while but am only now trying to see why.

When I do an service command ie

Code: Select all

systemctl
Failed to get D-Bus connection: No connection to service manager.

or
qdbus
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


I have no idea how to try and restart it, or where to look. Is it a problem anyway?

Ta

Peter.

Context information is missing. Did you run this as user or root. If root, how did you switch to root?

Same response as root or user. To get to root, su a terminal.

Peter.

pnunn wrote:To get to root, su a terminal.

Only the half truth. The proper way to get root is using

Code: Select all

su -

because this also initializes environment variables and other stuff (cf su man page)

Also please show the output of

Code: Select all

systemctl status udev.service

and

Code: Select all

systemctl restart udev.service

OK.. thanks for that.. I didn't realize that...

Code: Select all

[pnunn@localhost] - [~] - [10033]
[$] su -                                                                                                                                                                                                [23:16:49]
Password:
[  8:22AM ]  [ root@localhost:~ ]
 $ systemctl
Failed to get D-Bus connection: No connection to service manager.
[  8:22AM ]  [ root@localhost:~ ]
 $ systemctl status udev.service
Failed to get D-Bus connection: No connection to service manager.
[  8:23AM ]  [ root@localhost:~ ]
$ systemctl restart udev.service
Failed to get D-Bus connection: No connection to service manager.


Thanks again.
Peter.

Please show the output of

Code: Select all

rpm -qa | grep udev

and

Code: Select all

rpm -qa | grep systemd

Code: Select all

 $ rpm -qa | grep udev
lib64udev0-173-3.mga2
lib64gudev1.0_0-173-3.mga2
libgudev1.0_0-173-3.mga2
udev-173-3.mga2
system-config-printer-udev-1.3.6-1.mga2
pyudev-0.12-1.mga2
libudev0-173-3.mga2
[  9:23AM ]  [ root@localhost:~ ]
 $ rpm -qa | grep systemd
lib64systemd-login0-37-9.mga2
systemd-37-9.mga2
lib64systemd-daemon0-37-9.mga2
systemd-units-37-9.mga2


Peter.

OK, now please show the output of

Code: Select all

systemctl status udev.service

but this time as normal user.

please install too :

systemd-sysvinit
systemd-units

and reboot

OK.. same result from systemctl status as normal user, but after installing systemd-sysvinit I now get

Code: Select all

 systemctl status udev.service                                                                                                                                                                   [17:03:45]
udev.service - udev Kernel Device Manager
          Loaded: loaded (/lib/systemd/system/udev.service; static)
          Active: active (running) since Wed, 09 Nov 2011 17:01:11 +1100; 2min 39s ago
        Main PID: 100 (udevd)
          CGroup: name=systemd:/system/udev.service
                  ├  100 /sbin/udevd
                  ├ 5278 /sbin/udevd
                  └ 5280 /sbin/udevd


as normal user, which is a bit more interesting .

However, I did notice on rebooting LOTS of failed messages coming up referring to various systemctl status reports that I needed to run (Networking being one, not sure what the others were).
but the only one in /var/log/messages is

Code: Select all

Nov  9 17:02:39 localhost dbus[2488]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Nov  9 17:02:39 localhost dbus-daemon[2488]: dbus[2488]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Nov  9 17:02:39 localhost dbus[2488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Nov  9 17:02:39 localhost dbus-daemon[2488]: dbus[2488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.


Peter.