Bug 2130605 - crash in sync_update_persist_op() of content sync plugin [NEEDINFO]
Summary: crash in sync_update_persist_op() of content sync plugin
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.9
Assignee: thierry bordaz
QA Contact: LDAP QA Team
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-28 15:20 UTC by Anton Bobrov
Modified: 2023-08-10 13:25 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-21 11:02:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:
vashirov: needinfo? (mreynolds)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 5407 0 None closed sync_repl crashes if enabled while dynamic plugin is enabled 2023-08-10 13:23:33 UTC
Red Hat Issue Tracker IDMDS-3233 0 None None None 2023-06-21 15:44:54 UTC
Red Hat Issue Tracker RHELPLAN-150324 0 None None None 2023-03-01 16:44:13 UTC

Description Anton Bobrov 2022-09-28 15:20:32 UTC
Description of problem:

The ns-slapd is crashing in sync_update_persist_op() of content sync plugin:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  sync_update_persist_op (pb=pb@entry=0x7f37da578b00, e=0x7f37d43da840, eprev=eprev@entry=0x0, 
    op_tag=op_tag@entry=104, label=label@entry=0x7f38177e9404 "sync_add_persist_post_op")
    at ldap/servers/plugins/sync/sync_persist.c:250
250         for (curr_op = prim_op; curr_op; curr_op = curr_op->next) {
[Current thread is 1 (Thread 0x7f37d61f8700 (LWP 65068))]
(gdb) bt
#0  0x00007f38177e7836 in sync_update_persist_op
    (pb=pb@entry=0x7f37da578b00, e=0x7f37d43da840, eprev=eprev@entry=0x0, op_tag=op_tag@entry=104, label=label@entry=0x7f38177e9404 "sync_add_persist_post_op") at ldap/servers/plugins/sync/sync_persist.c:250
#1  0x00007f38177e7d4d in sync_add_persist_post_op (pb=0x7f37da578b00)
    at ldap/servers/plugins/sync/sync_persist.c:371
#2  0x00007f382565fcb9 in plugin_call_func
    (list=0x7f3818b5e500, operation=operation@entry=550, pb=pb@entry=0x7f37da578b00, call_one=call_one@entry=0)
    at ldap/servers/slapd/plugin.c:2032
#3  0x00007f382565ff04 in plugin_call_list (pb=0x7f37da578b00, operation=550, list=<optimized out>)
    at ldap/servers/slapd/plugin.c:1973
#4  0x00007f382565ff04 in plugin_call_plugins
    (pb=pb@entry=0x7f37da578b00, whichfunction=whichfunction@entry=550) at ldap/servers/slapd/plugin.c:442
#5  0x00007f3814901ae0 in ldbm_back_add (pb=0x7f37da578b00) at ldap/servers/slapd/back-ldbm/ldbm_add.c:1413
#6  0x00007f38255faf58 in op_shared_add (pb=pb@entry=0x7f37da578b00) at ldap/servers/slapd/add.c:692
#7  0x00007f38255fbff7 in do_add (pb=pb@entry=0x7f37da578b00) at ldap/servers/slapd/add.c:236
#8  0x00005654d21e71e9 in connection_dispatch_operation
    (pb=0x7f37da578b00, op=<optimized out>, conn=<optimized out>) at ldap/servers/slapd/connection.c:620
#9  0x00005654d21e71e9 in connection_threadmain () at ldap/servers/slapd/connection.c:1785
#10 0x00007f3822094968 in _pt_root (arg=0x7f380fda9040) at ../../.././nspr/pr/src/pthreads/ptthread.c:201
#11 0x00007f3821a2f1cf in start_thread (arg=<optimized out>) at pthread_create.c:479
#12 0x00007f3823ce2dd3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Version-Release number of selected component (if applicable):

RHEL 8.6 / 389-ds-base-1.4.3.28-7.module+el8.6.0+15293+4900ec12.x86_64


How reproducible:

No local reproducer but the crash happens occasionally in production env.


Additional info:

Full bt will follow as attachment.

Comment 23 mreynolds 2023-06-21 15:40:53 UTC
Any update on the hotfix testing?

Comment 24 Têko Mihinto 2023-06-21 16:50:24 UTC
(In reply to mreynolds from comment #23)
> Any update on the hotfix testing?

Hi Mark,

Just checked the customer case and there was no crash since the hotfix was applied.

Regards,
Têko.


Note You need to log in before you can comment on or make changes to this bug.