Bug 724033 - kadmin fails to start when using a custom DAL driver
kadmin fails to start when using a custom DAL driver
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5 (Show other bugs)
6.1
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Nalin Dahyabhai
BaseOS QE Security Team
:
Depends On: 723723
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-21 14:16 EDT by Nalin Dahyabhai
Modified: 2011-12-06 12:37 EST (History)
5 users (show)

See Also:
Fixed In Version: krb5-1.9-16.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 723723
Environment:
Last Closed: 2011-12-06 12:37:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nalin Dahyabhai 2011-07-21 14:16:07 EDT
+++ 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 12:37:03 EST
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.