Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 504195[details]
gdb backtrace
Description of problem:
Segmentation fault when certmonger service is started and messagebus service was already stopped
Version-Release number of selected component (if applicable):
certmonger-0.42-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1.install certmonger
2.stop messagebus service
3.start certmonger service
Actual results:
[root@dhcp201-117 yum.repos.d]# service certmonger start
Starting certmonger: process 1409: arguments to dbus_connection_set_exit_on_disconnect() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3003.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
/bin/bash: line 1: 1409 Segmentation fault /usr/sbin/certmonger -S -p /var/run/certmonger.pid
[FAILED]
Expected results:
No Segmentaion fault and proper error message for messagebus service status.
Additonal info:
(1)gdb bt attached.
Verified.
RHEL Version:
=============
[root@dhcp201-220 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.2 Beta (Santiago)
Certmonger Version:
==================
[root@dhcp201-220 ~]# rpm -q certmonger
certmonger-0.46-1.el6.x86_64
Steps used to verify:
=====================
(1)Install certmonger
[root@dhcp201-220 ~]# yum install certmonger
Loaded plugins: product-id, subscription-manager
Updating certificate-based repositories.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package certmonger.x86_64 0:0.46-1.el6 will be installed
--> Finished Dependency Resolution
Installed products updated.
Installed:
certmonger.x86_64 0:0.46-1.el6
Complete!
(2)stop messagebus service
[root@dhcp201-220 ~]# service messagebus status
messagebus (pid 1458) is running...
[root@dhcp201-220 ~]# service messagebus stop
Stopping system message bus: [ OK ]
(3)start certmonger service
[root@dhcp201-220 ~]# service certmonger status
certmonger is stopped
[root@dhcp201-220 ~]# service certmonger start
Starting certmonger: Error connecting to D-Bus.
Please verify that the message bus (D-Bus) service is running.
[FAILED]
[root@dhcp201-220 ~]#
Result:
=======
Now, there is no segfault and proper message is displayed for messagebus service status.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1708.html
Created attachment 504195 [details] gdb backtrace Description of problem: Segmentation fault when certmonger service is started and messagebus service was already stopped Version-Release number of selected component (if applicable): certmonger-0.42-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.install certmonger 2.stop messagebus service 3.start certmonger service Actual results: [root@dhcp201-117 yum.repos.d]# service certmonger start Starting certmonger: process 1409: arguments to dbus_connection_set_exit_on_disconnect() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3003. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace /bin/bash: line 1: 1409 Segmentation fault /usr/sbin/certmonger -S -p /var/run/certmonger.pid [FAILED] Expected results: No Segmentaion fault and proper error message for messagebus service status. Additonal info: (1)gdb bt attached.