[389-users] Re: Crash with SEGV after compacting

2023-07-11 Thread Mathieu Baudier
Hello, thank you for your quick answer! The OP of this thread has already posted a backtrace: https://lists.pagure.io/archives/list/389-users@lists.fedoraproject.org/message/JOV45YZSNTY7IN72TGHBVYRFLDFCQNWN/ We use the same version as the OP (1.4.4.11) : $ sudo apt list 389-ds-base

[389-users] Re: Crash with SEGV after compacting

2023-07-11 Thread Mark Reynolds
On 7/11/23 9:43 AM, Thierry Bordaz wrote: Hello, Unfortunately the original backtrace did not contain symbol and I can not say if the bug was already fixed Thread 1 (Thread 0x7f7c42a4e700 (LWP 22323)): #0 0x7f7c54258c9c in ??? () at

[389-users] Re: Crash with SEGV after compacting

2023-07-11 Thread Thierry Bordaz
Hello, Unfortunately the original backtrace did not contain symbol and I can not say if the bug was already fixed Thread 1 (Thread 0x7f7c42a4e700 (LWP 22323)): #0 0x7f7c54258c9c in ??? () at /usr/lib/x86_64-linux-gnu/dirsrv/plugins/libback-ldbm.so #1 0x7f7c5425b4c4 in ??? () at

[389-users] Re: Crash with SEGV after compacting

2023-07-11 Thread Thierry Bordaz
Hi, What version are you running ? Are you running a replicated topology, what is the crashing server (supplier, consumer, hub) ? Do you have a backtrace of the crash (with debugsource) ? Unfortunately I doubt compaction can be disabled (it is part of the checkpointing that is mandatory).

[389-users] Re: Crash with SEGV after compacting

2023-07-11 Thread Mathieu Baudier
Hello, we have exactly the same problem (also on Debian 11). 389-ds crashes when compacting. Is there a related bug ticket to track? Is it possible / advisable to disable compacting? (our instances are critical but very small, with only credentials in them) If yes, how can it be done? Thanks