0003564: yum-updatesd not working after upgrade to centos 5.3

(0009188)
Marcuccio (reporter)
2009-04-17 14:43

I forgot to say that I have exactly the same issue on two different desktop pc (different hw but similar software configuration).

(0009190)
etfong (reporter)
2009-04-18 01:14

Having the same issue with a new 5.3 install with yum-updatesed dieing and dbus error with puplet

"Traceback (most recent call last):
  File "/usr/bin/puplet", line 467, in ?
    main()
  File "/usr/bin/puplet", line 464, in main
    p.run()
  File "/usr/bin/puplet", line 451, in run
    self._refreshInfo()
  File "/usr/bin/puplet", line 191, in _refreshInfo
    if self.updatesObject is not None and \
AttributeError: DBusException instance has no attribute '_dbus_error_name'

(0009353)
Phil Schaffner (reporter)
2009-05-13 15:04

A workaround has been posted in a forum thread:
http://www.centos.org/modules/newbb/viewtopic.php?post_id=76607&topic_id=20236&forum=38 [^]

(0009354)
ASI_Sysnet (reporter)
2009-05-14 10:05

Yum update doesn't work on CentOS 5.3 system configured like DNS server, I attached error log about yum.

ASI System & Network administrators.

(0009488)
BartSimpson (reporter)
2009-06-18 06:21

It is noted at upstream.
https://bugzilla.redhat.com/show_bug.cgi?id=480339 [^]

(0009807)
jhughes@hughesjr.com (administrator)
2009-08-25 12:16

I have built and made available dbus-python-0.82 as a temporary work around. You can get the RPM here:

http://people.centos.org/hughesjr/dbus-python-0.82/ [^]

Download the correct RPM for your arch and install it with the command:

rpm -Uvh dbus-python-0.82.4-2.el5_3.i386.rpm

OR

rpm -Uvh dbus-python-0.82.4-2.el5_3.x86_64.rpm

Then make sure yum-updatesd is installed and running.

NOTE: This will allow puplet to run and it is the solution that the upstream provider says they will implement. It might cause issues with other programs and should only be seen as a temporary fix.

(0010295)
ohw0571 (reporter)
2009-11-05 14:33

On my systems, the update notification is still not functional after upgrade to CentOS 5.4! Specifically, .xsession-errors still shows:

"Error getting update info: Message did not receive a reply (timeout by message b
us)
Introspect error: The name edu.duke.linux.yum was not provided by any .service f
iles
Traceback (most recent call last):
File "/usr/bin/puplet", line 191, in _refreshInfo
if self.updatesObject is not None and \
AttributeError: DBusException instance has no attribute '_dbus_error_name'"

Does this mean the problem still has not been fixed upstream? Quite annoying, although it is - admittedly - not a severe issue.

Issue History
Date Modified	Username	Field	Change
2009-04-16 16:24	Marcuccio	New Issue
2009-04-16 16:24	Marcuccio	Assigned To	=> kbsingh@karan.org
2009-04-16 16:24	Marcuccio	File Added: yum-updatesd.debug.log
2009-04-16 17:10	AlanBartlett	Issue Monitored: AlanBartlett
2009-04-17 14:43	Marcuccio	Note Added: 0009188
2009-04-18 01:14	etfong	Note Added: 0009190
2009-04-18 01:14	etfong	Issue Monitored: etfong
2009-04-19 22:39	toracat	Relationship added	related to 0003540
2009-04-20 12:40	range	Relationship added	has duplicate 0003565
2009-04-29 22:26	robhancock	Issue Monitored: robhancock
2009-05-13 15:04	Phil Schaffner	Note Added: 0009353
2009-05-14 09:58	ASI_Sysnet	Tag Attached: 5.3
2009-05-14 09:59	ASI_Sysnet	Tag Detached: 5.3
2009-05-14 10:00	ASI_Sysnet	File Added: yum-error-log.txt
2009-05-14 10:05	ASI_Sysnet	Note Added: 0009354
2009-06-18 06:21	BartSimpson	Note Added: 0009488
2009-06-18 06:21	BartSimpson	Issue Monitored: BartSimpson
2009-08-25 12:16	jhughes@hughesjr.com	Note Added: 0009807
2009-11-05 14:33	ohw0571	Note Added: 0010295

Notes
(0009188) Marcuccio (reporter) 2009-04-17 14:43	I forgot to say that I have exactly the same issue on two different desktop pc (different hw but similar software configuration).

(0009190) etfong (reporter) 2009-04-18 01:14	Having the same issue with a new 5.3 install with yum-updatesed dieing and dbus error with puplet "Traceback (most recent call last): File "/usr/bin/puplet", line 467, in ? main() File "/usr/bin/puplet", line 464, in main p.run() File "/usr/bin/puplet", line 451, in run self._refreshInfo() File "/usr/bin/puplet", line 191, in _refreshInfo if self.updatesObject is not None and \ AttributeError: DBusException instance has no attribute '_dbus_error_name'

(0009353) Phil Schaffner (reporter) 2009-05-13 15:04	A workaround has been posted in a forum thread: http://www.centos.org/modules/newbb/viewtopic.php?post_id=76607&topic_id=20236&forum=38 [^]

(0009354) ASI_Sysnet (reporter) 2009-05-14 10:05	Yum update doesn't work on CentOS 5.3 system configured like DNS server, I attached error log about yum. ASI System & Network administrators.

(0009488) BartSimpson (reporter) 2009-06-18 06:21	It is noted at upstream. https://bugzilla.redhat.com/show_bug.cgi?id=480339 [^]

(0009807) jhughes@hughesjr.com (administrator) 2009-08-25 12:16	I have built and made available dbus-python-0.82 as a temporary work around. You can get the RPM here: http://people.centos.org/hughesjr/dbus-python-0.82/ [^] Download the correct RPM for your arch and install it with the command: rpm -Uvh dbus-python-0.82.4-2.el5_3.i386.rpm OR rpm -Uvh dbus-python-0.82.4-2.el5_3.x86_64.rpm Then make sure yum-updatesd is installed and running. NOTE: This will allow puplet to run and it is the solution that the upstream provider says they will implement. It might cause issues with other programs and should only be seen as a temporary fix.

(0010295) ohw0571 (reporter) 2009-11-05 14:33	On my systems, the update notification is still not functional after upgrade to CentOS 5.4! Specifically, .xsession-errors still shows: "Error getting update info: Message did not receive a reply (timeout by message b us) Introspect error: The name edu.duke.linux.yum was not provided by any .service f iles Traceback (most recent call last): File "/usr/bin/puplet", line 191, in _refreshInfo if self.updatesObject is not None and \ AttributeError: DBusException instance has no attribute '_dbus_error_name'" Does this mean the problem still has not been fixed upstream? Quite annoying, although it is - admittedly - not a severe issue.