RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1200340 - DBusException: Error.NoReply: Message did not receive a reply (timeout by message bus)
Summary: DBusException: Error.NoReply: Message did not receive a reply (timeout by mes...
Keywords:
Status: CLOSED DUPLICATE of bug 1207306
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel67
TreeView+ depends on / blocked
 
Reported: 2015-03-10 10:50 UTC by Rehana
Modified: 2015-05-15 19:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-07 18:21:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1198976 0 unspecified CLOSED traceback when you auto-attach and remove subscriptions on a vm registered using proxy 2021-02-22 00:41:40 UTC

Internal Links: 1198976

Description Rehana 2015-03-10 10:50:39 UTC
Description of problem:
Observed dbus exception after subscription removal on the guest machine. Also a crash report was available on the machine

Version-Release number of selected component (if applicable):
# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.45-1
subscription management rules: 5.14
subscription-manager: 1.14.1-1.el6
python-rhsm: 1.14.1-1.el6


How reproducible:
Not always

Steps to Reproduce:
1.# subscription-manager list --consumed
+-------------------------------------------+
   Consumed Subscriptions
+-------------------------------------------+
Subscription Name:   Awesome OS Virtual Datacenter
Provides:            Awesome OS Server Bits
SKU:                 awesomeos-virt-datacenter
Contract:            3
Account:             12331131231
Serial:              907046992398743178
Pool ID:             ff8080814be9bfc9014c033f7c9b2908
Provides Management: No
Active:              True
Quantity Used:       1
Service Level:       
Service Type:        
Status Details:      Subscription is current
Subscription Type:   Standard
Starts:              03/04/2015
Ends:                03/03/2016
System Type:         Virtual

2 # subscription-manager remove --all
1 subscription removed at the server.
1 local certificate has been deleted.
Traceback (most recent call last):
  File "/usr/share/rhsm/subscription_manager/dbus_interface.py", line 59, in emit_status
    self.validity_iface.emit_status()
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)


Actual results:
observed dbus exceptions on the machine


Additional info:
crash report details
------------------

[root@dhcp47-182 entitlement]# mail
Heirloom Mail version 12.4 7/29/08.  Type ? for help.
"/var/spool/mail/root": 7 messages 1 new 3 unread
    1 ABRT Daemon           Mon Mar  9 09:21 114/5191  "[abrt] a crash has been detected"
    2 ABRT Daemon           Tue Mar 10 04:49 114/5197  "[abrt] a crash has been detected again"
 U  3 ABRT Daemon           Tue Mar 10 05:49 114/5196  "[abrt] a crash has been detected again"
 U  4 ABRT Daemon           Tue Mar 10 05:57 114/5196  "[abrt] a crash has been detected again"
    5 ABRT Daemon           Tue Mar 10 06:07 114/5197  "[abrt] a crash has been detected again"
    6 ABRT Daemon           Tue Mar 10 06:23 114/5197  "[abrt] a crash has been detected again"
>N  7 ABRT Daemon           Tue Mar 10 06:39 113/5186  "[abrt] a crash has been detected again"
& 7
Message  7:
From DoNotReply.bos.redhat.com  Tue Mar 10 06:39:15 2015
Return-Path: <DoNotReply.bos.redhat.com>
X-Original-To: root@localhost
Delivered-To: root.bos.redhat.com
Date: Tue, 10 Mar 2015 06:39:15 -0400
From: ABRT Daemon <DoNotReply.bos.redhat.com>
To: root.bos.redhat.com
Subject: [abrt] a crash has been detected again
User-Agent: Heirloom mailx 12.4 7/29/08
Content-Type: text/plain; charset=us-ascii
Status: R

abrt_version:   2.0.8
cmdline:        /usr/bin/python -S /usr/sbin/subscription-manager remove --all
executable:     /usr/sbin/subscription-manager
hostname:       dhcp47-182.lab.bos.redhat.com
kernel:         2.6.32-540.el6.x86_64
last_occurrence: 1425983955
machineid:      sosreport_uploader-dmidecode=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       subscription-manager
pkg_release:    1.el6
pkg_version:    1.14.1
time:           Mon 09 Mar 2015 09:21:37 AM EDT
uid:            0
username:       root

backtrace:
:connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
:
:Traceback (most recent call last):
:  File "/usr/share/rhsm/subscription_manager/dbus_interface.py", line 59, in emit_status
:    self.validity_iface.emit_status()
:  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
:    return self._proxy_method(*args, **keywords)
:  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
:    **keywords)
:  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
:    message, timeout)
:DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
:
:Local variables in innermost frame:
:byte_arrays: False
:self: <dbus._dbus.SystemBus (system) at 0x2cdf2f0>
:args: ()
:utf8_strings: False
:bus_name: 'com.redhat.SubscriptionManager'
:get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
:object_path: '/EntitlementStatus'
:timeout: -1.0
:signature: ''
:dbus_interface: 'com.redhat.SubscriptionManager.EntitlementStatus'
:message: <dbus.lowlevel.MethodCallMessage object at 0x7f5d703958e8>
:method: 'emit_status'

event_log:
:/usr/libexec/abrt-action-generate-machine-id:113: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
:  .format(sd, ex.message))
:Machine-ID generator 'systemd' failed: Could not use systemd's machine-id: [Errno 2] No such file or directory: '/etc/machine-id'
:
:** COLLECTED WARNINGS **
:Failed to open memory buffer (/dev/mem): Permission denied
:No SMBIOS nor DMI entry point found, sorry.
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:Permission denied to memory file/device (/dev/mem)
:** END OF WARNINGS **

Comment 1 Devan Goodwin 2015-04-07 18:21:02 UTC

*** This bug has been marked as a duplicate of bug 1207306 ***


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