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 636894 - certmonger fails to start on new install
Summary: certmonger fails to start on new install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: certmonger
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: Jenny Severance
URL:
Whiteboard:
Depends On: 636876 636893
Blocks: 642407
TreeView+ depends on / blocked
 
Reported: 2010-09-23 15:52 UTC by Dmitri Pal
Modified: 2011-05-19 13:07 UTC (History)
5 users (show)

Fixed In Version: certmonger-0.30-2
Doc Type: Bug Fix
Doc Text:
Previously, after installing the certmonger utility, the certmonger service failed to start. This occurred because the package installation did not signal the system bus daemon that it needed to re-read its configuration as to allow the certmonger daemon to connect to the bus. This update fixes the bug and the certmonger service can be started right after the installation.
Clone Of: 636893
Environment:
Last Closed: 2011-05-19 13:07:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0570 0 normal SHIPPED_LIVE certmonger bug fix and enhancement update 2011-05-19 09:37:40 UTC

Comment 1 Dmitri Pal 2010-09-23 15:53:58 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
After installing certmonger the system needs to be rebooted for the certmonger to start properly.
Comment 2 Nalin Dahyabhai 2010-10-19 20:47:56 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-After installing certmonger the system needs to be rebooted for the certmonger to start properly.+After installing certmonger, the system message bus daemon needs to be signalled to reload its configuration in order for it to allow the certmonger service to start properly.  This can be done by sending the dbus-daemon process a SIGHUP signal or by rebooting the system.  This will be handled automatically in subsequent releases of the certmonger package.
Comment 4 Ryan Lerch 2010-10-20 07:36:58 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-After installing certmonger, the system message bus daemon needs to be signalled to reload its configuration in order for it to allow the certmonger service to start properly.  This can be done by sending the dbus-daemon process a SIGHUP signal or by rebooting the system.  This will be handled automatically in subsequent releases of the certmonger package.+After installing certmonger, the system message bus daemon needs to be signalled to reload its configuration to allow the certmonger service to start properly.  To work around this issue, send the dbus-daemon process a SIGHUP signal, or, alterntively, reboot the system.
Comment 6 Kaleem 2011-03-11 09:20:51 UTC 
Verified

RHEL version:

[root@localhost ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.1 Beta (Santiago)

Certmonger version:

[root@localhost ~]# rpm -qi certmonger | head
Name        : certmonger                   Relocations: (not relocatable)
Version     : 0.34                              Vendor: Red Hat, Inc.
Release     : 1.el6                         Build Date: Fri 14 Jan 2011 08:30:16 PM IST
Install Date: Wed 09 Mar 2011 05:25:48 PM IST      Build Host: x86-004.build.bos.redhat.com
Group       : System Environment/Daemons    Source RPM: certmonger-0.34-1.el6.src.rpm
Size        : 683642                           License: GPLv3+
Signature   : (none)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://certmonger.fedorahosted.org
Summary     : Certificate status monitor and PKI enrollment client

Steps used to verify:

(1)install certmonger
 
   [root@localhost ~]# rpm -Uvh certmonger-0.34-1.el6.x86_64.rpm 
Preparing...                ########################################### [100%]
   1:certmonger             ########################################### [100%]

(2)start certmonger service

[root@localhost ~]# service certmonger start
Starting certmonger:                                       [  OK  ]

 
Results:
certmonger service started successfully after installation without sending SIGHUP signal to dbus-daemon or reboot of system.
Comment 7 Eva Kopalova 2011-05-02 17:02:08 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-After installing certmonger, the system message bus daemon needs to be signalled to reload its configuration to allow the certmonger service to start properly.  To work around this issue, send the dbus-daemon process a SIGHUP signal, or, alterntively, reboot the system.+Previously, after installing the certmonger utility, the certmonger service failed to start. This occurred because the package installation did not signal the system bus daemon that it needed to re-read its configuration as to allow the certmonger daemon to connect to the bus. This update fixes the bug and the certmonger service can be started right after the installation.
Comment 8 errata-xmlrpc 2011-05-19 13:07:12 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0570.html
Note You need to log in before you can comment on or make changes to this bug.