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 is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47756

Heavily nested DIT LDIF files can take a long time when generating numsubordinates and ancestorIDs.  There is no logging during these phases and it can appear that the import is hung.

There are also some internal "loops" in the import code that do not check for "aborts", and can actually hang the server if you attempt to stop it.

Hi Mark, could you provide the steps to verify?
Thanks!

Verification steps

Test that a shutdown aborts an online import

[1]  Setup a DS instance using dc=example,dc=com
[2]  Create a 300k entry ldif
[3]  Run ldif2db.pl:

         ldif2db.pl -Z INSTANCE -n userroot -D "cn=directory manager" -w Secret123 -i <LDIF FILE>

[4]  Wait 5 seconds to allow the import to get started
[5]  Stop the DS (this should not timeout or appear to "hang")
[6]  Grep the errors log for "Aborting all Import threads"

$ rpm -qa  | grep 389
389-ds-base-1.3.3.1-9.el7.x86_64
389-ds-base-debuginfo-1.3.3.1-9.el7.x86_64
389-ds-base-libs-1.3.3.1-9.el7.x86_64

I followed verification steps in #c4

$ grep Abort /var/log/dirsrv/slapd-rhel7ds/errors
[11/Dec/2014:00:58:45 +0100] - import userRoot: Aborting all Import threads...

Server didn't timeout or appear to hang. 
Marking as VERIFIED.

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://rhn.redhat.com/errata/RHSA-2015-0416.html