[389-users] Re: Questions re: Replication Change Log Management

Hi Paul,

Another reason the the change log might not be trimmed is if there is a replication agreement that has not sent some of those changes yet.  I think it can also happen if there is an obsolete replica in the RUV.

Check the ruv with this command (adjust the suffix of course):  

    # dsconf slapd-localhost replication get-ruv --suffix dc=example,dc=com

If you see a replica RUV element that is out of place you can remove it using the cleanallruv task

    # dsconf slapd-localhost repl-tasks cleanallruv --suffix dc=example,dc=com --replica-id <the ID> --force-cleaning

You can also enable replication error logging and check for trimming events.  Trimming is probably still happening, but perhaps it's not a lot of entries:

    # dsconf slapd-localhost logging error set level replication

And when you're done you can do:

    # dsconf slapd-localhost logging error set level default

HTH,

Mark

On 10/1/26 2:50 PM, Paul Whitney via 389-users wrote:

Good afternoon,

We are running 389-DS version 2.8.0-10.  We have a multi-supplier replication agreement in place and each supplier to hub and then to consumers.  We have a changelog retention policy of 7 days (the default).  Lately we are noticing very large replication-changelog.db files to the tune of about 17-22 GB.  The 7-day retention policy doesnt seem to be truncating the size of these files as relication chages are aged off.  I have tried setting the max size of the db to 10 GB, but that did not make a difference and then changed the trim-interval setting to every 5 minutes.  Still no change in the db file size.  Is there a better way to manage this cleanly?

Thank you,

Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.

-- 
Identity Management Development Team

-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[389-users] Questions re: Replication Change Log Management

Good afternoon, We are running 389-DS version 2.8.0-10. We have a multi-supplier replication agreement in place and each supplier to hub and then to consumers. We have a changelog retention policy of 7 days (the default). Lately we are noticing very large replication-changelog.db files to the tune of about 17-22 GB. The 7-day retention policy doesnt seem to be truncating the size of these files as relication chages are aged off. I have tried setting the max size of the db to 10 GB, but that did not make a difference and then changed the trim-interval setting to every 5 minutes. Still no change in the db file size. Is there a better way to manage this cleanly? Thank you, Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.

-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Test Days: Anaconda installer new features in Fedora 45

Greetings testers!

Please join us for upcoming Test Days and help us improve Fedora's quality and stability. Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.

This time, we'll focus on new features in Anaconda (the installer) in Fedora 45: WebUI for Atomic desktops, Remote WebUI and Stratis support.

Test period: 2026-09-28 to 2026-10-02
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-09-28_Anaconda_F45_features

Thank you for your contributions!

--

Kamil Paral (he/him/his)

Fedora Quality

-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] 2026-09-28 @ 15:00 UTC - Fedora Quality Meeting

# Fedora Quality Assurance Meeting # Date: 2026-09-28 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting&iso=20260928T15&p1=1440&ah=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 45 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] 2026-09-28 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

# F45 Blocker Review meeting # Date: 2026-09-28 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20260928T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org 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/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20260927.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20260927.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: python-blivet - 20260924.n.0: python-blivet-3.14.2-1.fc45.src, 20260927.n.0: python-blivet-3.14.2-2.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 RISC-V (non-official) Beta images are available!

(Also on Discourse: https://discussion.fedoraproject.org/t/fedora-45-risc-v-non-official-beta-images-are-available/) Hi, folks! The Fedora 45 RISC-V (non-official, community-contributed) *Beta* images are available for testing. You can find the Server, Cloud, and Container artifacts here: https://dl.fedoraproject.org/pub/alt/risc-v/releases/test/45_Beta/ Notes on server images ---------------------- There are two kinds of server images available: • Fedora-Server-Host-Generic: This image uses the standard 7.2 kernel (7.2.7-300.0.riscv64.fc45). This kernel is very close to upstream, and will work on VisionFive 2, Orange Pi RV, Milk-V Mars, and probably other boards. • Fedora-Server-Host-Omni: This image uses the Fedora "Omni" kernel, (7.2.7-300.0.riscv64.omni.fc45). The "Omni" aims to work on a wider range of RISC-V boards. Some patches in this kernel are still under review upstream. For details on the list of boards the Omni kernel should work on, refer to the overview[1] of Omni kernel. Please take these images for a spin[2] and let us know if you hit any issues. Most of the active discussion is on the Fedora RISC-V Matrix channel[2]. Regards, Fedora RISC-V Community (but any errors are mine) [1] https://copr.fedorainfracloud.org/coprs/g/forge-riscv-members/riscv64_omni_kernel/ [2] https://fedoraproject.org/wiki/Architectures/RISC-V/QEMU [3] https://chat.fedoraproject.org/#/room/#riscv:fedoraproject.org PS: Usually we send these out just to Fedora Discourse, trying to include the lists as well from this release :-) -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new