Announcing the creation of a new nightly release validation test event
for Fedora 44 Branched 20260217.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:
anaconda - 20260214.n.0: anaconda-44.20-1.fc44.src, 20260217.n.0: anaconda-44.21-1.fc44.src
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44
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_44_Branched_20260217.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260217.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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
Fedora Info
Wednesday, February 18, 2026
[Test-Announce]Fedora 44 Branched 20260214.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event
for Fedora 44 Branched 20260214.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:
anaconda - 20260211.n.0: anaconda-44.18-1.fc44.src, 20260214.n.0: anaconda-44.20-1.fc44.src
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44
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_44_Branched_20260214.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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
for Fedora 44 Branched 20260214.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:
anaconda - 20260211.n.0: anaconda-44.18-1.fc44.src, 20260214.n.0: anaconda-44.20-1.fc44.src
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44
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_44_Branched_20260214.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260214.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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 44 Branched 20260211.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event
for Fedora 44 Branched 20260211.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
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44
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_44_Branched_20260211.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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
for Fedora 44 Branched 20260211.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
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44
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_44_Branched_20260211.n.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260211.n.0_Security_Lab
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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-IoT 44 RC 20260205.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event
for Fedora-IoT 44 RC 20260205.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
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44iot
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-IoT_44_RC_20260205.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20260205.0_General
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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
for Fedora-IoT 44 RC 20260205.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
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44iot
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-IoT_44_RC_20260205.0_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20260205.0_General
Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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
[fedora-arm] Re: CPU temperature
On Mon, 16 Feb 2026 at 16:10, David Legg <dwlegg@gmail.com> wrote:
>
> Would one expect this to book on an RPI4 too?
Not sure what you mean by that question.
> It's now serving web pages very nicely on my RPI 5 :)
>
> :D
>
> On 21/01/2026 00:57, Peter Robinson wrote:
> > Hi David,
> >
> >> Is there a way of monitoring CPU temperature for Fedora aarch64 RPI 5
> >> yet, please?
> > tmon in the kernel-tools package is a tool to do that, I don't believe
> > patches have been posted yet to do thermal management which is I think
> > what you're actually asking about.
> >
> > Peter
> >
> > I have been away, I have you other email on my list to reply to but
> > haven't got to it in my backlog yet.
--
_______________________________________________
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
>
> Would one expect this to book on an RPI4 too?
Not sure what you mean by that question.
> It's now serving web pages very nicely on my RPI 5 :)
>
> :D
>
> On 21/01/2026 00:57, Peter Robinson wrote:
> > Hi David,
> >
> >> Is there a way of monitoring CPU temperature for Fedora aarch64 RPI 5
> >> yet, please?
> > tmon in the kernel-tools package is a tool to do that, I don't believe
> > patches have been posted yet to do thermal management which is I think
> > what you're actually asking about.
> >
> > Peter
> >
> > I have been away, I have you other email on my list to reply to but
> > haven't got to it in my backlog yet.
--
_______________________________________________
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
Tuesday, February 17, 2026
[Test-Announce]Fedora 44 Beta Freeze and Bodhi updates-testing activation point
Hi all,
Today's an important day on the Fedora Linux 44 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 44 packages must be submitted to updates-testing and pass
the relevant requirements [3] before they will be marked as 'stable' and
moved to the Fedora Repository.
Today is also the Beta freeze [4]. This means that only packages which
fix accepted blocker or freeze exception bugs [5][6] will be marked as
'stable' and included in the Beta composes. Other builds will remain in
updates-testing until the Beta release is approved, at which point the
Beta freeze is lifted and packages can move to 'stable' as usual until
the Final freeze.
Today is also the Software String freeze [7], which means that strings
marked for translation in Fedora-translated projects should not now be
changed for Fedora Linux 44.
Finally, today is the 'completion deadline' Change Checkpoint [8],
meaning that Fedora Linux 44 Changes must now be 'feature complete or
close enough to completion that a majority of its functionality can be
tested'. All tracking bugs should be on ON_QA state or later to reflect
this.
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-44/f-44-key-tasks.html
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
[8] https://fedoraproject.org/wiki/Changes/Policy
--
_______________________________________________
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
Today's an important day on the Fedora Linux 44 schedule [1], with
several significant cut-offs. First of all, today is the Bodhi
updates-testing activation point [2]. That means that from now all
Fedora Linux 44 packages must be submitted to updates-testing and pass
the relevant requirements [3] before they will be marked as 'stable' and
moved to the Fedora Repository.
Today is also the Beta freeze [4]. This means that only packages which
fix accepted blocker or freeze exception bugs [5][6] will be marked as
'stable' and included in the Beta composes. Other builds will remain in
updates-testing until the Beta release is approved, at which point the
Beta freeze is lifted and packages can move to 'stable' as usual until
the Final freeze.
Today is also the Software String freeze [7], which means that strings
marked for translation in Fedora-translated projects should not now be
changed for Fedora Linux 44.
Finally, today is the 'completion deadline' Change Checkpoint [8],
meaning that Fedora Linux 44 Changes must now be 'feature complete or
close enough to completion that a majority of its functionality can be
tested'. All tracking bugs should be on ON_QA state or later to reflect
this.
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-44/f-44-key-tasks.html
[2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
[3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
[4] https://fedoraproject.org/wiki/Milestone_freezes
[5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
[8] https://fedoraproject.org/wiki/Changes/Policy
--
_______________________________________________
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
Monday, February 16, 2026
[389-users] 389ds 2.5 deployment issue
This past weekend I finally replaced the last of our DS 1.3 instances (1.3.6.12 to be exact). We did a lot of testing but what happened in production with a full prod workload was quite surprising.
This 1.3 instance has been in operation for over a decade and has never had any issues with memory usage (it has 16GB total). When we moved the 2.5 instance into production, the amount of memory usage quickly rose to over 16GB, causing AWS ECS to kill the task. I tried upping the instance type to r6i.xlarge (32GB) and that quickly ran out of memory too. r6i.2xlarge also failed with excessive memory consumption. It wasn't until I switched to r6i.4xlarge (128GB) that the instances finally more or less stabilized at approx. 60GB of memory use.
Other info:
- This is using bdb, not mdb.
- We tried to keep the cn=config values as close as possible to the original instance.
- Over a year ago, we did the same thing with a different production system (moved it to 2.5 bdb) and it's typically consuming about 32GB in spite of being a significantly larger database.
- We used the same docker image from docker hub for both of these systems (2.5.0 B2024.017.0000).
For the system we moved this past weekend, here are some daily stats:
SRCH Events BIND Events MOD Events SRCH/BIND
2026-01-01T00:00:00.000-0700 71422 18013 1136 397%
2026-01-02T00:00:00.000-0700 88233 26273 1958 336%
2026-01-03T00:00:00.000-0700 71724 20275 1512 354%
2026-01-04T00:00:00.000-0700 90487 26763 2271 338%
2026-01-05T00:00:00.000-0700 232190 69743 5602 333%
2026-01-06T00:00:00.000-0700 270592 65322 5752 414%
2026-01-07T00:00:00.000-0700 288077 73869 6021 390%
2026-01-08T00:00:00.000-0700 276662 69352 6309 399%
2026-01-09T00:00:00.000-0700 265886 62109 4992 428%
2026-01-10T00:00:00.000-0700 201912 33331 2528 606%
2026-01-11T00:00:00.000-0700 229512 44090 2956 521%
2026-01-12T00:00:00.000-0700 333711 97047 6494 344%
2026-01-13T00:00:00.000-0700 384455 121332 7049 317%
2026-01-14T00:00:00.000-0700 544805 202567 10667 269%
2026-01-15T00:00:00.000-0700 523023 180011 38875 291%
2026-01-16T00:00:00.000-0700 393932 121466 27357 324%
2026-01-17T00:00:00.000-0700 235071 47104 10557 499%
2026-01-18T00:00:00.000-0700 269432 64199 9329 420%
2026-01-19T00:00:00.000-0700 299010 76743 9937 390%
2026-01-20T00:00:00.000-0700 501148 176427 16488 284%
2026-01-21T00:00:00.000-0700 466164 164206 13574 284%
2026-01-22T00:00:00.000-0700 422490 141143 9041 299%
2026-01-23T00:00:00.000-0700 360027 109641 8832 328%
2026-01-24T00:00:00.000-0700 230624 48358 5385 477%
2026-01-25T00:00:00.000-0700 292855 75711 7428 387%
2026-01-26T00:00:00.000-0700 449129 151908 11426 296%
2026-01-27T00:00:00.000-0700 433417 146937 9902 295%
2026-01-28T00:00:00.000-0700 425190 142981 9832 297%
2026-01-29T00:00:00.000-0700 401043 132635 8418 302%
2026-01-30T00:00:00.000-0700 350886 102997 6616 341%
2026-01-31T00:00:00.000-0700 235397 49611 4578 474%
The system we moved earlier has 10 times as much search traffic as this one, but this one gets up to 4 times as many binds.
Any thoughts on what might be going on here?
Tim
--
_______________________________________________
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
This 1.3 instance has been in operation for over a decade and has never had any issues with memory usage (it has 16GB total). When we moved the 2.5 instance into production, the amount of memory usage quickly rose to over 16GB, causing AWS ECS to kill the task. I tried upping the instance type to r6i.xlarge (32GB) and that quickly ran out of memory too. r6i.2xlarge also failed with excessive memory consumption. It wasn't until I switched to r6i.4xlarge (128GB) that the instances finally more or less stabilized at approx. 60GB of memory use.
Other info:
- This is using bdb, not mdb.
- We tried to keep the cn=config values as close as possible to the original instance.
- Over a year ago, we did the same thing with a different production system (moved it to 2.5 bdb) and it's typically consuming about 32GB in spite of being a significantly larger database.
- We used the same docker image from docker hub for both of these systems (2.5.0 B2024.017.0000).
For the system we moved this past weekend, here are some daily stats:
SRCH Events BIND Events MOD Events SRCH/BIND
2026-01-01T00:00:00.000-0700 71422 18013 1136 397%
2026-01-02T00:00:00.000-0700 88233 26273 1958 336%
2026-01-03T00:00:00.000-0700 71724 20275 1512 354%
2026-01-04T00:00:00.000-0700 90487 26763 2271 338%
2026-01-05T00:00:00.000-0700 232190 69743 5602 333%
2026-01-06T00:00:00.000-0700 270592 65322 5752 414%
2026-01-07T00:00:00.000-0700 288077 73869 6021 390%
2026-01-08T00:00:00.000-0700 276662 69352 6309 399%
2026-01-09T00:00:00.000-0700 265886 62109 4992 428%
2026-01-10T00:00:00.000-0700 201912 33331 2528 606%
2026-01-11T00:00:00.000-0700 229512 44090 2956 521%
2026-01-12T00:00:00.000-0700 333711 97047 6494 344%
2026-01-13T00:00:00.000-0700 384455 121332 7049 317%
2026-01-14T00:00:00.000-0700 544805 202567 10667 269%
2026-01-15T00:00:00.000-0700 523023 180011 38875 291%
2026-01-16T00:00:00.000-0700 393932 121466 27357 324%
2026-01-17T00:00:00.000-0700 235071 47104 10557 499%
2026-01-18T00:00:00.000-0700 269432 64199 9329 420%
2026-01-19T00:00:00.000-0700 299010 76743 9937 390%
2026-01-20T00:00:00.000-0700 501148 176427 16488 284%
2026-01-21T00:00:00.000-0700 466164 164206 13574 284%
2026-01-22T00:00:00.000-0700 422490 141143 9041 299%
2026-01-23T00:00:00.000-0700 360027 109641 8832 328%
2026-01-24T00:00:00.000-0700 230624 48358 5385 477%
2026-01-25T00:00:00.000-0700 292855 75711 7428 387%
2026-01-26T00:00:00.000-0700 449129 151908 11426 296%
2026-01-27T00:00:00.000-0700 433417 146937 9902 295%
2026-01-28T00:00:00.000-0700 425190 142981 9832 297%
2026-01-29T00:00:00.000-0700 401043 132635 8418 302%
2026-01-30T00:00:00.000-0700 350886 102997 6616 341%
2026-01-31T00:00:00.000-0700 235397 49611 4578 474%
The system we moved earlier has 10 times as much search traffic as this one, but this one gets up to 4 times as many binds.
Any thoughts on what might be going on here?
Tim
--
_______________________________________________
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
Subscribe to:
Comments (Atom)