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.

Bug 1163023

Summary: certmonger 32 bits crashes after upgrading from 6.5 to 6.6
Product: Red Hat Enterprise Linux 6 Reporter: Natxo Asenjo <natxo>
Component: certmongerAssignee: Jan Cholasta <jcholast>
Status: CLOSED ERRATA QA Contact: Kaleem <ksiddiqu>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.6CC: dkupka, dpal, mkosek, nalin, nsoman
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: certmonger-0.77.1-1.el6 Doc Type: Bug Fix
Doc Text:
Prior to this update, after the user upgraded from Red Hat Enterprise Linux 6.5 to Red Hat Enterprise Linux 6.6 and rebooted the system, certmonger in some cases erroneously exited shortly after starting or performed a series of unnecessary checks for new certificates. A patch has been applied to fix this bug, and these problems no longer occur in the described situation.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 07:17:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Natxo Asenjo 2014-11-12 09:09:01 UTC 
Description of problem:

after upgrading from 6.5 to 6.6 the certmonger daemon crashes on 32 bit hosts

Version-Release number of selected component (if applicable):


How reproducible:

always.

Steps to Reproduce:
1. update a host running centos 6.5 to centos 6.6
2. reboot
3. certmonger stops

Actual results:
certmonger stops working

Expected results:
certmonger keeps working

Additional info:
See mailing list thread "certmonger question" on freeipa-users: https://www.redhat.com/archives/freeipa-users/2014-November/msg00156.html
Comment 2 Nalin Dahyabhai 2014-11-12 14:20:25 UTC 
Where you able to check if the current snapshot package from https://jdennis.fedorapeople.org/ipa-devel/rhel/6/i386/os/ fixes the problem?
Comment 3 Natxo Asenjo 2014-11-12 15:04:31 UTC 
Sorry, I just read your message. 

I have just tried it on one of the 6.6 hosts and it works!

Nice work, thanks.
Comment 6 Kaleem 2015-03-30 09:30:44 UTC 
Verified.

Certmonger version:
===================
[root@dhcp207-106 ~]# rpm -q certmonger
certmonger-0.77.1-1.el6.i686
[root@dhcp207-106 ~]#
Comment 8 errata-xmlrpc 2015-07-22 07:17:32 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.

https://rhn.redhat.com/errata/RHBA-2015-1379.html