Bug 691790 - Unable to install IPA Server, since certmonger cannot start
Summary: Unable to install IPA Server, since certmonger cannot start
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: certmonger
Version: 6.1
Hardware: Unspecified
OS: Unspecified
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-03-29 13:29 UTC by Namita Soman
Modified: 2011-03-29 14:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-29 14:16:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Namita Soman 2011-03-29 13:29:00 UTC 
Description of problem:
When installing IPA server, got error that - 
2011-03-29 09:00:59,626 DEBUG args=/sbin/service certmonger start
2011-03-29 09:00:59,626 DEBUG stdout=Starting certmonger: internal error

And IPA server install failed.

Version-Release number of selected component (if applicable):
certmonger-0.40-1.20110329T0537z.el6.x86_64

How reproducible:


Steps to Reproduce:
1.Install IPA Server
2.
3.
  
Actual results:
got error:
  [16/32]: configuring ssl for ds instance
Unexpected error - see ipaserver-install.log for details:
 Command '/sbin/service certmonger start ' returned non-zero exit status 1
:: [   FAIL   ] :: Installing IPA Server (Expected 0, got 1)


Expected results:
Install should succeed


Additional info:
Comment 1 Namita Soman 2011-03-29 13:31:17 UTC 
Also tried:

[root@qe-blade-04 log]# /usr/sbin/certmonger -d 99 start
internal error
Comment 2 Nalin Dahyabhai 2011-03-29 14:16:34 UTC 
Whoops, this bug went in after 0.40 when I was adding some sanity checks for startup-time (mainly for the per-user instance, which has to use getenv() or getpwuid() to find the user's home directory, in case both fail).  Not in 0.40 proper, and won't be in 0.41, either.
Note You need to log in before you can comment on or make changes to this bug.