#48922 ns-slapd crashes during the deletion of backend
Closed: wontfix None Opened 5 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1355760

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
Crash in TET test suite for distribution logic plugin. During the test backend is deleted and this causes the crash:

Program terminated with signal 11, Segmentation fault.
#0  __db_refresh (dbp=dbp@entry=0x7f7218001260, txn=txn@entry=0x0,
flags=flags@entry=0,
    deferred_closep=deferred_closep@entry=0x7f72537fcac4, reuse=reuse@entry=0)
at ../../src/db/db.c:884
884                     if (dbc->txn != NULL)
(gdb) bt
#0  __db_refresh (dbp=dbp@entry=0x7f7218001260, txn=txn@entry=0x0,
flags=flags@entry=0,
    deferred_closep=deferred_closep@entry=0x7f72537fcac4, reuse=reuse@entry=0)
at ../../src/db/db.c:884
#1  0x00007f7261e21eb6 in __db_close (dbp=dbp@entry=0x7f7218001260,
txn=txn@entry=0x0, flags=flags@entry=0) at ../../src/db/db.c:744
#2  0x00007f7261e33e32 in __db_close_pp (dbp=0x7f7218001260, flags=0) at
../../src/db/db_iface.c:261
#3  0x00007f725ef6b9ee in dblayer_close_indexes (be=be@entry=0x7f71fc006db0) at
ldap/servers/slapd/back-ldbm/dblayer.c:2510
#4  0x00007f725ef6bb02 in dblayer_instance_close (be=0x7f71fc006db0) at
ldap/servers/slapd/back-ldbm/dblayer.c:2556
#5  0x00007f725ef8138a in import_main_offline (arg=<optimized out>) at
ldap/servers/slapd/back-ldbm/import.c:1469
#6  0x00007f7268d6896b in _pt_root (arg=0x7f720800d9a0) at
../../../nspr/pr/src/pthreads/ptthread.c:212
#7  0x00007f7268708dc5 in start_thread (arg=0x7f72537fe700) at
pthread_create.c:308
#8  0x00007f72684376ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113


Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.10-3.el7.x86_64

How reproducible:
Non-deterministically, I had 2 crashes out of 10 runs.

Steps to Reproduce:
Run an import on a backend, and at the same time delete the backend config entry from cn=config

8cfb650..6c77c37 master -> master
commit 6c77c37
Author: Mark Reynolds mreynolds@redhat.com
Date: Wed Jul 13 16:24:19 2016 -0400

96da572..a64a2e9 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit a64a2e9
Author: Mark Reynolds mreynolds@redhat.com
Date: Wed Jul 13 16:24:19 2016 -0400

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.4.11

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1981

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

a year ago

Login to comment on this ticket.

Metadata