--On Saturday, December 03, 2016 6:42 PM -0500 Brendan Kearney bpk678@gmail.com wrote:
where do i chase down the source of roughly 10k messages a week, given that this is my home network? do i have a bottleneck in ldap? is bind-dyndb-ldap pounding on ldap for some unknown reason? i dont believe this to an appropriate amount of logs for what seems to be a low volume network.
Hi Brendan,
a) This has nothing to do with MMR/Mirror Mode
b) It's not uncommon, and it rarely indicates a problem. Again, you would need to show that things are actually being deferred for a significant amount of time. Most often it is only for milliseconds. I.e., it's an informational message that may or may not be indicative of a real issue.
Overall, you haven't really provided a lot of the necessary information to help you move forward, such as:
OpenLDAP release OpenLDAP backend(s) in use Thread settings concurrency settings Specific messages of the problem
etc
For example, it could be the application(s) are poorly written, and fail to use persistent connections, causing binds to be constantly be deferred. Or it could be searches being deferred, etc. I.e., we have no idea /which/ operations are being deferred because you haven't provided that information.
I personally prefer applying the patch to OpenLDAP that provides timing information for every operation so that I can actually tell whether or not real problems are occurring. If that interests you, I can point you at it.
Hope that helps!
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com