Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 227874 - No device/cpu data on some machines
No device/cpu data on some machines
Product: Fedora
Classification: Fedora
Component: smolt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McGrath
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-02-08 13:22 EST by David Rees
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 0.9.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-03 12:38:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
machine1.txt (779 bytes, text/plain)
2007-02-08 13:22 EST, David Rees
no flags Details
machine2.txt (962 bytes, text/plain)
2007-02-08 13:23 EST, David Rees
no flags Details
machine3.txt (953 bytes, text/plain)
2007-02-08 13:24 EST, David Rees
no flags Details

  None (edit)
Description David Rees 2007-02-08 13:22:29 EST
Description of problem:
smolt does not report any device data for some machines. Some errors are
generated (which vary slightly on the affected machines).

Version-Release number of selected component (if applicable):

How reproducible:
Every time.

Steps to Reproduce:
1. Run smoltSendProfile
Actual results:
I have 3 machines that differ slightly in output. I'll attach the output from
each (after removing the UUID). But the common errors generated by each is below:

Error reading hardware information: dbus_bindings.DBusException
Error reading DMI information: dbus_bindings.DBusException

Expected results:
Expect to see a device list and proper CPU information.
Comment 1 David Rees 2007-02-08 13:22:30 EST
Created attachment 147686 [details]
Comment 2 David Rees 2007-02-08 13:23:25 EST
Created attachment 147687 [details]
Comment 3 David Rees 2007-02-08 13:24:08 EST
Created attachment 147688 [details]
Comment 4 Mike McGrath 2007-02-08 14:07:59 EST
I'm currently in the process of re-writing the dbus bindings for smolt, would
you be willing to be a test subject when the time comes?
Comment 5 David Rees 2007-02-08 14:10:24 EST
Yep, I can help with any testing you need.
Comment 6 David Rees 2007-02-14 15:12:31 EST
I see that smolt-0.8-1.fc6 was released. On one system I got the following stack
trace because messagebus wasn't running:

Traceback (most recent call last):
  File "/usr/bin/smoltSendProfile", line 60, in ?
    profile = smolt.Hardware()
  File "/usr/share/smolt/client/smolt.py", line 158, in __init__
    systemBus = dbus.SystemBus()
  File "/usr/lib/python2.4/site-packages/dbus/_dbus.py", line 260, in __new__
    return Bus.__new__(cls, Bus.TYPE_SYSTEM, use_default_mainloop, private)
  File "/usr/lib/python2.4/site-packages/dbus/_dbus.py", line 99, in __new__
    bus._connection = dbus_bindings.bus_get(bus_type, private)
  File "dbus_bindings.pyx", line 1692, in dbus_bindings.bus_get
dbus_bindings.DBusException: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory

After I started up messagebus, I got this stack trace:

Introspect error: The name org.freedesktop.Hal was not provided by any .service
Traceback (most recent call last):
  File "/usr/bin/smoltSendProfile", line 60, in ?
    profile = smolt.Hardware()
  File "/usr/share/smolt/client/smolt.py", line 160, in __init__
    all_dev_lst = mgr.GetAllDevices()
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 25, in __call__
    ret = self._proxy_method (*args, **keywords)
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 102, in __call__
    reply_message = self._connection.send_with_reply_and_block(message, timeout)
  File "dbus_bindings.pyx", line 455, in
dbus_bindings.DBusException: The name org.freedesktop.Hal was not provided by
any .service files
Comment 7 Mike McGrath 2007-02-14 15:38:38 EST
Is hal running?

/etc/init.d/haldaemon status

I need to add a more graceful error.
Comment 8 David Rees 2007-02-14 16:07:37 EST
Much better.

I agree, printing a better error message for when messagebus and haldaemon
aren't running would be a perfect way to fix this issue.
Comment 9 Jared Smith 2007-03-03 12:13:18 EST
I'm seeing something similar, but slightly different.  I get the following error:

Send this information to the Smolt server? (y/n) y
Transmitting ...
Server Message: "Critical: Device Read Failed -
4388|0|None|None|ieee1394|Unknown|None|Unknown (0x001124)"
Comment 10 Mike McGrath 2007-03-03 12:38:12 EST
Should be fixed now.

Note You need to log in before you can comment on or make changes to this bug.