dbus problems.

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

dbus problems.

Postby pnunn » Nov 8th, '11, 02:12

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.
pnunn
 
Posts: 97
Joined: Jun 20th, '11, 14:22

Re: dbus problems.

Postby doktor5000 » Nov 8th, '11, 13:38

Context information is missing. Did you run this as user or root. If root, how did you switch to root?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18051
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: dbus problems.

Postby pnunn » Nov 8th, '11, 14:16

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

Peter.
pnunn
 
Posts: 97
Joined: Jun 20th, '11, 14:22

Re: dbus problems.

Postby doktor5000 » Nov 8th, '11, 17:01

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
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18051
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: dbus problems.

Postby pnunn » Nov 8th, '11, 23:26

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.
pnunn
 
Posts: 97
Joined: Jun 20th, '11, 14:22

Re: dbus problems.

Postby doktor5000 » Nov 9th, '11, 00:00

Please show the output of
Code: Select all
rpm -qa | grep udev
and
Code: Select all
rpm -qa | grep systemd
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18051
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: dbus problems.

Postby pnunn » Nov 9th, '11, 00:24

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.
pnunn
 
Posts: 97
Joined: Jun 20th, '11, 14:22

Re: dbus problems.

Postby doktor5000 » Nov 9th, '11, 00:35

OK, now please show the output of
Code: Select all
systemctl status udev.service
but this time as normal user.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18051
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: dbus problems.

Postby dmorgan » Nov 9th, '11, 03:07

please install too :

systemd-sysvinit
systemd-units

and reboot
dmorgan
 
Posts: 1
Joined: Mar 15th, '11, 22:00

Re: dbus problems.

Postby pnunn » Nov 9th, '11, 08:09

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.
pnunn
 
Posts: 97
Joined: Jun 20th, '11, 14:22


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron