Hello:

We are running an older 389-Directory Server (v 1.2.11.29) --- being upgraded soon but still stuck with it.

Starting a week ago, we have started receiving error messages like below --- restarting resolves till the next time error reoccurs (and service subsequently not responsive till restart).

Any ideas on how to find the root cause to what triggers it?

> [07/Sep/2017:06:18:03 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:03 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:03 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:03 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:04 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:04 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:04 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:04 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:05 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:06 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:06 -0700] - libdb: unable to allocate memory for mutex; resize mutex region

> [07/Sep/2017:06:18:06 -0700] - libdb: unable to allocate memory for mutex; resize mutex region