Re: Crash with SEGV after compacting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxxxxx/message/JOV45YZSNTY7IN72TGHBVYRFLDFCQNWN/

We use the same version as the OP (1.4.4.11) :

$ sudo apt list 389-ds-base
389-ds-base/oldstable,now 1.4.4.11-2 amd64 [installed]

which is the one provided by Debian 11 / bullseye, and which has not changed for a while.

We don't use replication on these instances.

If this backtrace is not sufficient, I am happy to reproduce the steps on a dedicated environment.

Dependening on your analysis, we will probably have to notify Debian, but I am not sure whether they will want to patch it for Debian 11.
So, maybe I will have to look at Debian 12 / bookworm (the new 'Debian stable'), and see whether the issue still occurs.

Cheers,

Mathieu

On Tue, 2023-07-11 at 11:51 +0200, Thierry Bordaz wrote:
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). It can be delayed with compaction
interval or timeof day but not suppressed.

best regards
thierry

On 7/11/23 09:51, Mathieu Baudier wrote:
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 in advance!

Mathieu
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux