Bug 724033 - kadmin fails to start when using a custom DAL driver
Summary: kadmin fails to start when using a custom DAL driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 723723
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-21 18:16 UTC by Nalin Dahyabhai
Modified: 2011-12-06 17:37 UTC (History)
5 users (show)

Fixed In Version: krb5-1.9-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 723723
Environment:
Last Closed: 2011-12-06 17:37:03 UTC
Target Upstream Version:

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


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

Description Nalin Dahyabhai 2011-07-21 18:16:07 UTC 
+++ This bug was initially created as a clone of Bug #723723 +++

The init script explicitly checks for a database file or pretend the db_library to be kldap.

I have a custom driver and the check fails.

At most the kadmin init script may check if db_library is present w/o trying to guess what value it should be set to.

But most probably it would be better to skip the check altogether and let kadmin log in /var/log/kadmin.log that there are errors.

The situation is particularly hard to discover because the initscript output is completely suppressed in F15 when systemctl gets involved.

I had to run it with SYSTEMCTL_SKIP_REDIRECT=1 to finally get the error and find out what was going on.
Comment 3 errata-xmlrpc 2011-12-06 17:37:03 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-1707.html
Note You need to log in before you can comment on or make changes to this bug.