# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 514289 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 514289 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

On Oct 11, 2017, at 11:57 AM, Quanah Gibson-Mount quanah@symas.com wrote:

--On Wednesday, October 11, 2017 10:44 AM -0700 Scott Classen sclassen@lbl.gov wrote:

...

Hello,

I've built openldap 2.4.45 on a CentOS 7.4.1708 machine with the following configuration:

I've seen this happen when a ulimit value was unreasonably small. Check the limits on -m or -v perhaps.

--Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com