Fedora Info

Thursday, May 14, 2026

[Test-Announce] Fedora-IoT 45 RC 20260514.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora-IoT 45 RC 20260514.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/45iot 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_45_RC_20260514.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20260514.0_General 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

Wednesday, May 13, 2026

[389-users] Re: Cannot change nsslapd-db-max-locks

On 5/13/26 4:03 PM, Orion Poplawski via 389-users wrote: > On 5/13/26 13:44, Mark Reynolds wrote: >> On 5/13/26 3:32 PM, Orion Poplawski via 389-users wrote: >>> So it seems that something is messed up with this particular host. >> The "db locks" are stored under /dev/shm/slapd-INSTANCE/ Perhaps there is >> not a lot of space allocated for /dev/shm on that host? > This is what it had: > > Filesystem Size Used Avail Use% Mounted on > tmpfs 1.5G 257M 1.3G 17% /dev/shm > > I bumped it a bit: > > Filesystem Size Used Avail Use% Mounted on > tmpfs 1.8G 289M 1.5G 17% /dev/shm > > Now I'm starting to think that I'm looking at two different things as the > nsslapd-db-max-locks is increasing after boot: > > nsslapd-db-current-locks: 52 > nsslapd-db-max-locks: 72 > > nsslapd-db-current-locks: 99 > nsslapd-db-max-locks: 174 > > nsslapd-db-current-locks: 101 > nsslapd-db-max-locks: 178 > > So maybe the reason I see a large value on one machine is more indicative that > something went haywire on it making it hit the configured maximum. Not sure, I know that the monitor stats you are looking at come directly from libdb and not the core server - so it's kind of a black box. It would require debugging libdb to see why it's behaving this way. > > > > -- 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

F44 election nominations now open

The Fedora Project is now accepting nominations for all elected bodies until May 21, 2026. Candidates can self-nominate or be nominated by others with prior consent. Interviews are mandatory and must be completed by May 28, 2026. Elected members serve a two-release term.

https://communityblog.fedoraproject.org/f44-election-nominations-now-open/

Justin Wheeler (he/him) || 📧 jwheel@redhat.com || 🔗 jwheel.org

Formerly Justin W. Flory

Fedora Community Architect
TZ=America/Atlanta (UTC-4) 🕗

Fedora is a registered Digital Public Good

While I may be sending this email outside my normal office hours, I have no expectation to receive a reply outside yours.

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

[389-users] Re: Cannot change nsslapd-db-max-locks

On 5/13/26 13:44, Mark Reynolds wrote: > > On 5/13/26 3:32 PM, Orion Poplawski via 389-users wrote: >> So it seems that something is messed up with this particular host. > The "db locks" are stored under /dev/shm/slapd-INSTANCE/ Perhaps there is > not a lot of space allocated for /dev/shm on that host? This is what it had: Filesystem Size Used Avail Use% Mounted on tmpfs 1.5G 257M 1.3G 17% /dev/shm I bumped it a bit: Filesystem Size Used Avail Use% Mounted on tmpfs 1.8G 289M 1.5G 17% /dev/shm Now I'm starting to think that I'm looking at two different things as the nsslapd-db-max-locks is increasing after boot: nsslapd-db-current-locks: 52 nsslapd-db-max-locks: 72 nsslapd-db-current-locks: 99 nsslapd-db-max-locks: 174 nsslapd-db-current-locks: 101 nsslapd-db-max-locks: 178 So maybe the reason I see a large value on one machine is more indicative that something went haywire on it making it hit the configured maximum. -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772-5637 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/

-- _______________________________________________ 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] Re: Cannot change nsslapd-db-max-locks

On 5/13/26 3:32 PM, Orion Poplawski via 389-users wrote: > On 5/13/26 07:41, Viktor Ashirov wrote: >> Hi, >> >> >> On Tue, May 12, 2026 at 4:46 PM Orion Poplawski via 389-users <389- >> users@lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org>> wrote: >> >> On one of our EL9 IPA servers I'm unable to change nsslapd-db-max-locks >> >> nsslapd-db-max-locks shows the peak concurrent lock count since the last >> restart. It's not meant to be changed. >> >> >> ldapsearch returns: >> >> # database, monitor, ldbm database, plugins, config >> dn: cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config >> nsslapd-db-current-locks: 96 >> nsslapd-db-max-locks: 179 >> >> dsconf config get returns: >> >> nsslapd-db-locks: 50018 >> >> I've restarted many times. Changed the value a couple of times. What's up? >> >> How exactly do you change them? >> This works for me: >> dsconf <instance> backend config set --locks 100000 >> >> After restart in the error logs: >> [13/May/2026:08:11:01.395692873 -0400] - NOTICE - bdb_start - Resizing max db >> lock count: 50000 -> 100000 > Yeah, I'm using dsconf backend config set to set it. I do see that message: > > [11/May/2026:09:39:25.771331509 -0600] - NOTICE - bdb_start - Resizing max db > lock count: 50000 -> 50018 > > and dsconf config get shows: > > nsslapd-db-locks: 50018 > > but the ldapsearch results stay small as above. > > Other machines the ldapsearch show the larger number: > > # database, monitor, ldbm database, plugins, config > dn: cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config > nsslapd-db-current-locks: 114 > nsslapd-db-max-locks: 50018 > > So it seems that something is messed up with this particular host. The "db locks" are stored under /dev/shm/slapd-INSTANCE/ Perhaps there is not a lot of space allocated for /dev/shm on that host? > > > -- 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] Re: Cannot change nsslapd-db-max-locks

On 5/13/26 07:41, Viktor Ashirov wrote: > Hi, > > > On Tue, May 12, 2026 at 4:46 PM Orion Poplawski via 389-users <389- > users@lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org>> wrote: > > On one of our EL9 IPA servers I'm unable to change nsslapd-db-max-locks > > nsslapd-db-max-locks shows the peak concurrent lock count since the last > restart. It's not meant to be changed. > > > ldapsearch returns: > > # database, monitor, ldbm database, plugins, config > dn: cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config > nsslapd-db-current-locks: 96 > nsslapd-db-max-locks: 179 > > dsconf config get returns: > > nsslapd-db-locks: 50018 > > I've restarted many times. Changed the value a couple of times. What's up? > > How exactly do you change them? > This works for me: > dsconf <instance> backend config set --locks 100000 > > After restart in the error logs: > [13/May/2026:08:11:01.395692873 -0400] - NOTICE - bdb_start - Resizing max db > lock count: 50000 -> 100000 Yeah, I'm using dsconf backend config set to set it. I do see that message: [11/May/2026:09:39:25.771331509 -0600] - NOTICE - bdb_start - Resizing max db lock count: 50000 -> 50018 and dsconf config get shows: nsslapd-db-locks: 50018 but the ldapsearch results stay small as above. Other machines the ldapsearch show the larger number: # database, monitor, ldbm database, plugins, config dn: cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config nsslapd-db-current-locks: 114 nsslapd-db-max-locks: 50018 So it seems that something is messed up with this particular host. -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772-5637 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/

[389-users] Re: Cannot change nsslapd-db-max-locks

Hi,

On Tue, May 12, 2026 at 4:46 PM Orion Poplawski via 389-users <389-users@lists.fedoraproject.org> wrote:

On one of our EL9 IPA servers I'm unable to change nsslapd-db-max-locks

nsslapd-db-max-locks shows the peak concurrent lock count since the last restart. It's not meant to be changed.

ldapsearch returns:

# database, monitor, ldbm database, plugins, config
dn: cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-current-locks: 96
nsslapd-db-max-locks: 179

dsconf config get returns:

nsslapd-db-locks: 50018

I've restarted many times. Changed the value a couple of times. What's up?

How exactly do you change them?

This works for me:

dsconf <instance> backend config set --locks 100000

After restart in the error logs:
[13/May/2026:08:11:01.395692873 -0400] - NOTICE - bdb_start - Resizing max db lock count: 50000 -> 100000

389-ds-base-2.7.0-12.el9_7.x86_64

--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of IT Systems 720-772-5637
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 https://www.nwra.com/

--
_______________________________________________
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

Viktor