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.
Description of problem:
IPA is not starting
# ipactl start -d
IPA version error: data needs to be upgraded (expected version '4.6.8-5.el7_9.4', current version '4.6.8-5.el7')
Automatically running upgrade, for details see /var/log/ipaupgrade.log
Be patient, this may take a few minutes.
ipa: DEBUG: Starting external process
ipa: DEBUG: args=/usr/sbin/ipa-server-upgrade
ipa: DEBUG: Process finished, return code=1
ipa: DEBUG: stdout=Upgrading IPA:. Estimated time: 1 minute 30 seconds
[1/9]: saving configuration
[2/9]: disabling listeners
[3/9]: enabling DS global lock
[4/9]: disabling Schema Compat
[5/9]: starting directory server
[error] CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1
[cleanup]: stopping directory server
[cleanup]: restoring configuration
ipa: DEBUG: stderr=IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually.
Unexpected error - see /var/log/ipaupgrade.log for details:
CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1
The ipa-server-upgrade command failed. See /var/log/ipaupgrade.log for more information
Automatic upgrade failed: IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually.
Unexpected error - see /var/log/ipaupgrade.log for details:
CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1
The ipa-server-upgrade command failed. See /var/log/ipaupgrade.log for more information
See the upgrade log for more details and/or run /usr/sbin/ipa-server-upgrade again
ipa: DEBUG: File "/usr/lib/python2.7/site-packages/ipaserver/install/installutils.py", line 1015, in run_script
return_value = main_function()
File "/sbin/ipactl", line 598, in main
ipa_start(options)
File "/sbin/ipactl", line 288, in ipa_start
version_check()
File "/sbin/ipactl", line 161, in version_check
raise IpactlError("Aborting ipactl")
ipa: DEBUG: The ipactl command failed, exception: IpactlError: Aborting ipactl
Aborting ipactl
Version-Release number of selected component (if applicable):
OS Version: Server 7.9 (Maipo)
ipa-server-4.6.8-5.el7_9.4.x86_64
389-ds-base-1.3.10.2-10.el7_9.x86_64
How reproducible:
The customer started facing this issue after upgrading IPA packages
Steps to Reproduce:
1. the customer updated to RHEL 7.9
2. after, when trying to start IPA, it failed with the above error
Actual results:
ipa: DEBUG: The ipactl command failed, exception: IpactlError: Aborting ipactl
Aborting ipactl
Expected results:
IPA services should successfuly start
Additional info:
the work around was to delete files /var/lib/sss/pubconf/krb5.include.d/
To sum up:
1. dirsrv not started is caused by SSSD krb5 locator temporary file
a. Bug 1952569 address this
b. sssd-2.6.1-1.el8 in RHEL 8.6 fixed it
2. Workaround for customer that have not get above fix:
Moving SSSD krb locator temporary file to other location, e.g.
mv /var/lib/sss/pubconf/krb5.include.d/krb5_libdefaultsXXXXXX /tmp
The KCS "'ipactl start' fails to start Directory Server" (https://access.redhat.com/solutions/6814721) has been written with the problem description, solution and workaround.
Comment 27Florence Blanc-Renaud
2022-03-15 07:04:16 UTC
The root of the issue is not the presence of the SSSD krb locator temporary file, but the *permissions* of the temporary file.
When IdM is configured, /etc/krb5.conf contains:
----- 8< -----
includedir /etc/krb5.conf.d/
includedir /var/lib/sss/pubconf/krb5.include.d/
...
----- >8 -----
As a consequence, kerberos client applications try to read all the files below /etc/krb5.conf.d/ and /var/lib/sss/pubconf/krb5.include.d/ and if one of them is not readable by the app, the initialization of the kerberos context fails.
The diagnostic can be done based on the content of dirsrv error log:
[root@server ~]# grep krb5_init_context /var/log/dirsrv/slapd-IPA-TEST/errors
[15/Mar/2022:06:56:49.822456662 +0000] - ERR - ipalockout_get_global_config - [file ipa_lockout.c, line 178]: krb5_init_context failed (-1429577697)
[15/Mar/2022:06:56:49.828182116 +0000] - ERR - ipaenrollment_start - [file ipa_enrollment.c, line 398]: krb5_init_context failed
[15/Mar/2022:06:56:49.834718739 +0000] - ERR - ipapwd_start - [file ipa_pwd_extop.c, line 1879]: krb5_init_context failed
Can the KCS be updated with the above information?
(In reply to Florence Blanc-Renaud from comment #27)
> Can the KCS be updated with the above information?
I have made the required modification. Please review
Comment 29Florence Blanc-Renaud
2022-03-15 08:50:55 UTC
Comment 34RHEL Program Management
2023-09-18 18:42:50 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 35RHEL Program Management
2023-09-18 18:45:00 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: IPA is not starting # ipactl start -d IPA version error: data needs to be upgraded (expected version '4.6.8-5.el7_9.4', current version '4.6.8-5.el7') Automatically running upgrade, for details see /var/log/ipaupgrade.log Be patient, this may take a few minutes. ipa: DEBUG: Starting external process ipa: DEBUG: args=/usr/sbin/ipa-server-upgrade ipa: DEBUG: Process finished, return code=1 ipa: DEBUG: stdout=Upgrading IPA:. Estimated time: 1 minute 30 seconds [1/9]: saving configuration [2/9]: disabling listeners [3/9]: enabling DS global lock [4/9]: disabling Schema Compat [5/9]: starting directory server [error] CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1 [cleanup]: stopping directory server [cleanup]: restoring configuration ipa: DEBUG: stderr=IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually. Unexpected error - see /var/log/ipaupgrade.log for details: CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1 The ipa-server-upgrade command failed. See /var/log/ipaupgrade.log for more information Automatic upgrade failed: IPA server upgrade failed: Inspect /var/log/ipaupgrade.log and run command ipa-server-upgrade manually. Unexpected error - see /var/log/ipaupgrade.log for details: CalledProcessError: Command '/bin/systemctl start dirsrv' returned non-zero exit status 1 The ipa-server-upgrade command failed. See /var/log/ipaupgrade.log for more information See the upgrade log for more details and/or run /usr/sbin/ipa-server-upgrade again ipa: DEBUG: File "/usr/lib/python2.7/site-packages/ipaserver/install/installutils.py", line 1015, in run_script return_value = main_function() File "/sbin/ipactl", line 598, in main ipa_start(options) File "/sbin/ipactl", line 288, in ipa_start version_check() File "/sbin/ipactl", line 161, in version_check raise IpactlError("Aborting ipactl") ipa: DEBUG: The ipactl command failed, exception: IpactlError: Aborting ipactl Aborting ipactl Version-Release number of selected component (if applicable): OS Version: Server 7.9 (Maipo) ipa-server-4.6.8-5.el7_9.4.x86_64 389-ds-base-1.3.10.2-10.el7_9.x86_64 How reproducible: The customer started facing this issue after upgrading IPA packages Steps to Reproduce: 1. the customer updated to RHEL 7.9 2. after, when trying to start IPA, it failed with the above error Actual results: ipa: DEBUG: The ipactl command failed, exception: IpactlError: Aborting ipactl Aborting ipactl Expected results: IPA services should successfuly start Additional info: the work around was to delete files /var/lib/sss/pubconf/krb5.include.d/