389-ds-base

#47841 chrash when deleting a replication agreement
Closed: wontfix Opened by lkrispen.

Closed: wontfix
Reopen Issue

Got a crash when deleting a replication agreement:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffa567fc700 (LWP 7242)]
0x00007ffa7266ab4b in prot_get_replica_object (rp=0x0) at ldap/servers/plugins/replication/repl5_protocol.c:154
154 return rp->replica_object;
(gdb) bt

0 0x00007ffa7266ab4b in prot_get_replica_object (rp=0x0) at ldap/servers/plugins/replication/repl5_protocol.c:154

1 0x00007ffa7265b52a in agmt_remove_maxcsn (ra=0x7ffa7d9432b0) at ldap/servers/plugins/replication/repl5_agmt.c:3041

2 0x00007ffa7265d338 in agmtlist_delete_callback (pb=0x7ffa567fbae0, e=0x7ffa300011c0, entryAfter=0x0, returncode=0x7ffa567f96a0, returntext=0x7ffa567f96f0 "", arg=0x0)

at ldap/servers/plugins/replication/repl5_agmtlist.c:625

3 0x00007ffa7c89703a in dse_call_callback (pdse=0x7ffa7d34bba0, pb=0x7ffa567fbae0, operation=32, flags=1, entryBefore=0x7ffa300011c0, entryAfter=0x0, returncode=0x7ffa567f96a0, returntext=0x7ffa567f96f0 "")

at ldap/servers/slapd/dse.c:2645

4 0x00007ffa7c896a47 in dse_delete (pb=0x7ffa567fbae0) at ldap/servers/slapd/dse.c:2513

5 0x00007ffa7c88a038 in op_shared_delete (pb=0x7ffa567fbae0) at ldap/servers/slapd/delete.c:364

6 0x00007ffa7c889847 in do_delete (pb=0x7ffa567fbae0) at ldap/servers/slapd/delete.c:128

7 0x00007ffa7cdc3b99 in connection_dispatch_operation (conn=0x7ffa7cc0c410, op=0x7ffa7d4e5cb0, pb=0x7ffa567fbae0) at ldap/servers/slapd/connection.c:650

8 0x00007ffa7cdc5b61 in connection_threadmain () at ldap/servers/slapd/connection.c:2534

9 0x00007ffa7acc4b46 in _pt_root (arg=0x7ffa7d95d620) at ../../../nspr/pr/src/pthreads/ptthread.c:204

10 0x00007ffa7a667d14 in start_thread (arg=0x7ffa567fc700) at pthread_create.c:309

11 0x00007ffa7a18568d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

could reproduce, the testcase seems to be simple

  • disable a replication agreement
  • try to delete this replication agreement

Interesting... I could reproduce the crash/abort on the master build, but not on the 1.3.2 build... It looks like a regression...

Duplicate of #47846.

Ludwig, could you move to the ticket and attach your patch to the ticket?

Metadata Update from @nhosoi:
- Issue set to the milestone: N/A

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/1172

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: Duplicate)
Metadata
None
None
None
None
Normal
None
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.