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.
Bug 1381153 - Crash in import_wait_for_space_in_fifo().
Summary: Crash in import_wait_for_space_in_fifo().
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1368209
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 09:15 UTC by Marcel Kolaja
Modified: 2022-07-09 07:49 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-81.el6_8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368209
Environment:
Last Closed: 2016-11-15 19:38:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2765 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-16 00:36:28 UTC

Description Marcel Kolaja 2016-10-03 09:15:46 UTC 
This bug has been copied from bug #1368209 and has been proposed
to be backported to 6.8 z-stream (EUS).
Comment 5 Sankar Ramalingam 2016-10-26 15:45:59 UTC 
Are there steps to reproduce/verify this issue? Based on my understanding, I need to import(online) large number of users with duplicate DNs. Can you please guide me if you already have steps to reproduce?
Comment 7 Sankar Ramalingam 2016-10-27 18:32:54 UTC 
Thanks Noriko for the steps. I followed the sequence of steps + online import + Add users simultaneously. However, I didn't encounter any crash with the server.

The error logs showed that the db file in not accessible.

 [27/Oct/2016:23:54:03 +051800] - WARNING---no write permission to file /var/lib/dirsrv/slapd-M1/db/example11189/id2entry.db4
[27/Oct/2016:23:54:03 +051800] - dbp->open("example11189/id2entry.db4") failed: Permission denied (13)
[27/Oct/2016:23:54:03 +051800] - Instance directory /var/lib/dirsrv/slapd-M1/db/example11189 may not be writable
[27/Oct/2016:23:54:03 +051800] - dblayer_instance_start fail: Permission denied (13)
[27/Oct/2016:23:54:03 +051800] - start: Failed to start databases, err=13 Permission denied
[27/Oct/2016:23:54:03 +051800] - Failed to start database plugin ldbm database
[27/Oct/2016:23:54:03 +051800] - WARNING: ldbm instance userRoot already exists


After that, I changed the permission for id2dbentry.db4 file, then the server is brought back alive.

chown dsuser.dsuser //var/lib/dirsrv/slapd-M1/db/example11189/id2entry.db4 

[root@vm-idm-006 slapd-M1]# service dirsrv restart
Shutting down dirsrv: 
    C1...[  OK  ]
    C2...[  OK  ]
    M1... server already stopped[FAILED]
  *** Error: 1 instance(s) unsuccessfully stopped[FAILED]
Starting dirsrv: 
    C1...[  OK  ]
    C2...[  OK  ]
    M1...[  OK  ]

Hence, marking the bug as Verified.
Comment 9 errata-xmlrpc 2016-11-15 19:38:42 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.

https://rhn.redhat.com/errata/RHSA-2016-2765.html
Note You need to log in before you can comment on or make changes to this bug.