Bug 712500 - Segmentation fault when certmonger service is started
Summary: Segmentation fault when certmonger service is started
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: certmonger
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-10 19:33 UTC by Kaleem
Modified: 2011-12-06 17:37 UTC (History)
3 users (show)

Fixed In Version: certmonger-0.45-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:37:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
gdb backtrace (1.24 KB, application/octet-stream)
2011-06-10 19:33 UTC, Kaleem
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1708 0 normal SHIPPED_LIVE certmonger bug fix update 2011-12-06 01:02:28 UTC

Description Kaleem 2011-06-10 19:33:47 UTC
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.

Comment 3 Kaleem 2011-09-22 12:48:03 UTC
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.

Comment 4 errata-xmlrpc 2011-12-06 17:37:45 UTC
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


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