Hide Forgot
Description of problem: Certmonger segfaults when the second instance is running and can't connect to D-Bus. $ service certmonger stop $ service certmonger start Starting certmonger: [ OK ] $ certmonger -S -n 2011-11-24 07:18:25 [13899] Unable to set well-known bus name "org.fedorahosted.certmonger": (2). Error connecting to D-Bus. Segmentation fault $ echo $? 139 $ service certmonger status certmonger (pid 13897) is running... $ service certmonger start $ service certmonger status certmonger (pid 13897) is running... $ service certmonger stop Stopping certmonger: [ OK ] $ service certmonger status certmonger is stopped $ certmonger -S -n Version-Release number of selected component (if applicable): certmonger-0.50-1.el5 How reproducible: Always Steps to Reproduce: See description part Actual results: Segfault. Expected results: No segfault, some error message expected. Additional info:
Verified. RHEL version: [root@ipa58client ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.8 Beta (Tikanga) Certmonger Version: [root@ipa58client ~]# rpm -q certmonger certmonger-0.50-3.el5 [root@ipa58client ~]# service certmonger status certmonger (pid 15930) is running... [root@ipa58client ~]# certmonger -S -n 2011-12-05 14:19:25 [17202] Unable to set well-known bus name "org.fedorahosted.certmonger": (2). Error connecting to D-Bus. [root@ipa58client ~]# Now, there is no segfault.
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-2012-0245.html