+++ This bug was initially created as a clone of Bug #500884 +++

Description of problem:
yum-updatesd requires the messagebus service to be running, even if it's configured to not use dbus.


Version-Release number of selected component (if applicable):
yum-updatesd-0.9-2.el5

How reproducible:
Always

Steps to Reproduce:
1. Modify /etc/yum/yum-updatesd.conf and set 'emit_via = syslog' and 'dbus_listener = no'
2. service messagebus stop
3. yum-updatesd -f -d -o
  
Actual results:
The number of available updates is published via syslog

Expected results:
yum-updatesd crashes with the error:
# yum-updatesd -f -d -o
Traceback (most recent call last):
  File "/usr/sbin/yum-updatesd", line 322, in ?
    main()
  File "/usr/sbin/yum-updatesd", line 282, in main
    checkUpdates(opts, wait = True)
  File "/usr/sbin/yum-updatesd", line 166, in checkUpdates
    bus = dbus.SystemBus()
  File "/usr/lib64/python2.4/site-packages/dbus/_dbus.py", line 260, in __new__
    return Bus.__new__(cls, Bus.TYPE_SYSTEM, use_default_mainloop, private)
  File "/usr/lib64/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: Connection refused


Additional info:
This is a serious problem when using a central syslog collector to determine which systems have updates available.  If messagebus crashes for any reason (as happened recently to me), then you no longer get syslog alerts that the (potentially many) remote systems need updating.

--- Additional comment from james.antill on 2009-05-14 13:22:39 EDT ---

 This should just be a simple copy of the same line from further down:

    try:
        bus = dbus.SystemBus()
    except dbus.DBusException, e:
        bus = None

...or even just move the "bus = dbus.SystemBus()" line 1 down, into the existing try/except.

 If you open a support ticket we can probably get this fixed for 5.4.x

--- Additional comment from wart on 2009-05-20 01:30:02 EDT ---

Filed as case # 1920624

--- Additional comment from pm-rhel on 2009-09-17 13:00:03 EDT ---

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

=======================================================


in addition to the hard to debug problem when messagebus is not running [there are no error messages of any kind to be found any where and you have to run it with "no-fork" in debug mode in order to find the problem at all; otherwise you will just feel like there are no updates available], the yum-updatesd package has no dependency on dbus and when installing yum-updatesd on a minimal system it will silently fail, as dbus is not installed on a minimal system.

yum-updatesd should depend on dbus

yum-updatesd should write error messages to the syslog [or to the configured emitter] if messagebus is not started instead of failing silently