[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