Bug 1045482 - Server does not start, cannot find unlocked certs
Summary: Server does not start, cannot find unlocked certs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: 389-ds-base
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 14:45 UTC by Michael Cronenworth
Modified: 2014-01-09 15:11 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.3.1.17-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 15:11:39 UTC
Type: Bug

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

Description Michael Cronenworth 2013-12-20 14:45:56 UTC 
Description of problem: After upgrading 389-ds-base and 389-ds-base-libs my LDAP server is not starting.

I get the same messages as described in:
http://web.archiveorange.com/archive/v/I3m7Y29eyXfV0pIkhEBU

The fix appears to not be pushed to Fedora 18 and 19.


Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.16-1.fc19.x86_64
389-ds-base-libs-1.3.1.16-1.fc19.x86_64

How reproducible: Always


Steps to Reproduce:
1. systemctl start dirsrv@ldap
2.
3.

Actual results: ns-slapd is not running


Expected results: ns-slapd is running


Additional info:
https://fedorahosted.org/389/ticket/47596
Comment 1 Noriko Hosoi 2014-01-08 23:09:42 UTC 
389-ds-base-1.3.1.17-1.fc19.x86_64 is available (or soon to be available) from the testing repository.  The version contains the patch for Ticket 47596 - "attrcrypt fails to find unlocked key".
(http://directory.fedoraproject.org/wiki/Releases/1.3.1.17)

It would be great if you could try the bits and give a karma/feedback.
https://admin.fedoraproject.org/updates/389-ds-base-1.3.1.17-1.fc19

Please note that Fedora 18 is not supported any more.
Comment 2 Michael Cronenworth 2014-01-08 23:21:53 UTC 
The updated package fixes this. I'll leave karma. Thanks!
Note You need to log in before you can comment on or make changes to this bug.