Re: Are smolt/dbus working well? (Re: New FC 8 kernel RPMS in updates)

[Jay Estabrook <Jay Estabrook hp com>]

The dbus updates probable were to fault, though (IMHO) not because
they were in error, just that it didn't get restarted properly.

So, (su)do (after the update is installed):

  service messagebus restart

And see if that helps.

If not, I'd suggest a reboot. Afterwards, you can check via:

  service messagebus status

at which time, you should see something like:

  dbus-daemon (pid 2406 1481) is running...

Note: the dbus update was my attempt to get rid of some of the
myriad unaligned accesses from that program.

Until proven wrong, it shouldn't have any adverse affect... ;-}

--Jay++

Steven Moix wrote:
> Hello,
> 
> I have similar errors since yesterday. When I start my 164LX/EV56
> system, I have to wait for HAL daemon to time out. The last yum activity
> was:
> 
> Apr 25 16:10:39 Updated: dbus-libs - 1.1.2-8.fc8.1axp.alpha
> Apr 25 16:10:46 Updated: dbus - 1.1.2-8.fc8.1axp.alpha
> Apr 25 16:10:47 Updated: dbus-x11 - 1.1.2-8.fc8.1axp.alpha
> Apr 25 16:12:46 Installed: libsmi - 0.4.5-2.fc8.alpha
> Apr 25 16:12:48 Installed: wireshark-gnome - 1.0.0-1.fc8.alpha
> Apr 26 12:39:42 Installed: poppler-utils - 0.6.2-1.fc8.alpha
> Apr 26 12:39:44 Installed: libXp - 1.0.0-8.fc8.alpha
> Apr 26 12:39:47 Installed: lesstif - 0.95.0-20.fc8.alpha
> Apr 26 12:39:49 Installed: libpaper - 1.1.22-1.fc8.1.alpha
> Apr 26 12:39:52 Installed: t1lib - 5.1.1-7.fc8.alpha
> Apr 26 12:39:57 Installed: xpdf - 1:3.02-4.fc8.alpha
> 
> And my /var/log/messages:
> 
> Apr 26 15:49:38 ev56 console-kit-daemon[1325]: WARNING: Couldn't connect
> to system bus: Did not receive a reply. Possible causes include: the
> remote applica
> tion did not send a reply, the message bus security policy blocked the
> reply, the reply timeout expired, or the network connection was broken.
> 
> Have a nice day
> Steven
> 
> 
> On Sat, 2008-04-26 at 22:48 +0900, Kazuyoshi Furutaka wrote:
>> Hi all,
>>
>> From: Oliver Falk <oliver linux-kernel at>
>> Subject: Re: New FC 8 kernel RPMS in updates
>> Date: Fri, 25 Apr 2008 11:41:18 +0200
>>
>>> Steven Moix wrote:
>>>>> but if you look at the smolt stats, they
>>>>>> don't seem to be updated...the stats are 2 weeks old.
>>>>> Hm. But I remember I looked a few days ago and alpha had a count of 5.
>>>>> So updates are happening...
>>>> There seems to be a cache problem somewhere. I tried to access the stats
>>>> on 2 different computers, with 2 different browsers and at EACH refresh
>>>> of the page, I get another date. April 9, 17 or 23 :)
>>> A few reloads and similar happens. I see alpha listed with count of 5
>>> and 7 :-(
>> On my alpha machine running the Fedora-8 based distro,
>> it seems that smolt is not working properly due to dbus
>> failure and that its profile was not sent.
>>
>>
>> When I try to send the profile, it failed as the following:
>>
>> [furutaka ram ~]$ smoltSendProfile
>>   Traceback (most recent call last):
>>     File "/usr/bin/smoltSendProfile", line 35, in <module>
>>       from scan import scan, rating
>>     File "/usr/share/smolt/client/scan.py", line 30, in <module>
>>       h = smolt.Hardware()
>>     File "/usr/share/smolt/client/smolt.py", line 336, in __init__
>>       raise SystemBusError, _('Could not bind to dbus.  Is dbus running?')
>>   smolt.SystemBusError: Could not bind to dbus.  Is dbus running?
>>
>>
>> On my x86_64 machine there're two dbus-daemon processes,
>>
>>   [furutaka peart ~]$ ps auxw|grep [d]bus-daemon
>>   dbus      1879  0.0  0.0  30068  1568 ?        Ssl  Apr03   0:03 \
>>     dbus-daemon --system
>>   furutaka  2549  0.0  0.0  30068  1112 ?        Ssl  Apr03   0:00 \
>>     /bin/dbus-daemon --fork --print-pid 4 --print-address 8 --session
>>
>> but NONE on the alpha machine.
>>
>>
>> Another symptom is start-up failure of some dbus dependent?
>> services during the boot:
>>   ...
>>   Starting wpa_supplicant: /etc/wpa_supplicant/wpa_supplicant.conf, , \
>>     dbus_bus_get[ctrl_iface_dbus]: Success Failed to initialize \
>>     wpa_supplicant
>>   ...
>>   Starting anacron: error: libhal_ctx_set_dbus_connection: \
>>     org.freedesktop.DBus.Error.NoServer: Failed to connect to socket \
>>     /var/run/dbus/system_bus_socket: Connection refused
>>
>>
>> Finally in /var/log/messages other system-bus related errors
>> were recorded:
>>   ...
>>   Apr 25 21:36:53 ram kernel: dbus-daemon(1399): unaligned trap at \
>>     000002000104085c: 000000011fe352c1 28 3
>>   Apr 25 21:36:53 ram kernel: dbus-daemon(1399): unaligned trap at \
>>     000002000104087c: 000000011fe352c1 2c 1
>>   ...
>>   Apr 26 22:06:14 ram console-kit-daemon[1541]: WARNING: Couldn't \
>>    connect to system bus: Failed to connect to socket \
>>    /var/run/dbus/system_bus_socket: Connection refused
>>   ...
>>   Apr 26 22:06:16 ram avahi-daemon[1574]: dbus_bus_get_private(): \
>>     Failed to connect to socket /var/run/dbus/system_bus_socket: \
>>     Connection refused
>>   Apr 26 22:06:16 ram avahi-daemon[1574]: WARNING: Failed to contact \
>>   D-Bus daemon.
>>
>>
>> Yours,
>> Kazuyoshi
>> --
>> Kazuyoshi Furutaka
>> furutaka jb3 so-net ne jp
>>
>> _______________________________________________
>> axp-list mailing list
>> axp-list redhat com
>> https://www.redhat.com/mailman/listinfo/axp-list
> 
> _______________________________________________
> axp-list mailing list
> axp-list redhat com
> https://www.redhat.com/mailman/listinfo/axp-list
>