> On 7 Oct 2020, at 17:39, Jan Kowalsky <jankow@xxxxxxxxxxxxxxxxxx> wrote: > > Hi all, > > suddenly one of our ldap-servers crashed and don't restart. > > When restarting dirsrv we find in logs: > > libdb: BDB2034 unable to allocate memory for mutex; resize mutex region > mmap in opening database environment failed trying to allocate 500000 > bytes. (OS err 12 - Cannot allocate memory) > > Same error, if we run dbverify. > > We are running version 3.5.17 of 389-ds on debian stretch: > > 389-ds 1.3.5.17-2 > > Ram doesn't seem to be the problem. Only 200 MB of 4GB is used. > > The server is part of a replicated cluster. Other servers (running same > software version - more or less on the same virtualisation hardware) are > not affected. > > But we got similar errors also some times in the past. But restarting > the service was always possible. > > Any ideas? > Given this is mmap and not malloc, is it possible you are hitting something like vm.max_map_count? I'm not sure what memory chunk size it's allocating but you could increase this parameter to see if that makes space for your mmap calls to function. The other things to check are ulimits and cgroups if you have any of those limits set in your system, Hope that helps, — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs, Australia _______________________________________________ 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
