On 06/12/2018 06:56 PM, Scott Mayo wrote: > Openldap version is 2.4.12 Seriously? This is really ancient release almost 10 years old. Being in your position my next task would be to update such an old system (not only because of OpenLDAP). > Logging region out of memory; you may need to increase its size > db_open(/var/lib/ldap/id2entry.bdb) failed: Cannot allocate memory (12). What does your monitoring say about memory usage before that log message?

Actually, I am moving to Windows 2016. :( Not because of me, but I plan on retiring in a few years and when I do, whoever comes after me will more than likely be a Windows guy and not Linux. I am trying to get everything ready for the next person when I leave. We live in a small Rural Community and there are virtually no techs around here that deal with Linux anymore.

Am Tue, 12 Jun 2018 11:56:23 -0500 schrieb Scott Mayo <smayo(a)bps14.org&gt;: > I just started getting this early this morning. I set this server up > a number of years ago. I am getting ready to put a new one in place, > but need to get this back up and going in the mean time. > > Openldap version is 2.4.12 > > /sbin/service ldap start > > Checking configuration files for slapd: [FAILED] > Logging region out of memory; you may need to increase its size > db_open(/var/lib/ldap/id2entry.bdb) failed: Cannot allocate memory > (12). backend_startup_one: bi_db_open failed! (12) > slap_startup failed (test would succeed using the -u switch) > stale lock files may be present in /var/lib/ldap [WARNING] > > Any ideas on what I need to check there? Thanks. The reference to -u switch leads to the impression that filesystem owwnership of slapd.conf and bdb database files is not appropriate. In addition you may check the database with BerkeleyDB tools, i.e. db_stat.