Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1143767 +++
Description of problem:
While working on test infrastructure for Kerberos5 I came across a weired error:
-- snip --
kadmin.local: Couldn't open log file /var/log/kadmind.log: Permission denied
-- snip --
At first this was confusing because I have a custom KRB5_KDC_PROFILE which explicitly use a script-defined location for such logs and not /var/log/ ...
... after some digging someone on IRC pointed out that kadmin/kadmind and other tools also source KRB5_CONFIG ... or if not present the default location /etc/krb5.conf ... which contained such a reference.
Problem is... this is not documented in the manpage.
Proposed fix:
Add a section "ENVIRONMENT" (like the POSIX manual pages have) to the manpages of the affected utilities (e.g. krb5kdc, kadmin, kadmin.local, kdb5_util, etc.) which lists the environment variables { KRB5_KDC_PROFILE, KRB5_CONFIG, ... }, the order in which they are sourced and the builtin default values if the variables are not set.
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.
https://access.redhat.com/errata/RHBA-2019:3516