On Thu, May 02, 2019 at 10:40:21AM +0000, i.harbuz@velcom.by wrote:
Any ldapsearch commands work fine if request doesn't hit into dynlist. If request hit in dynlist then it output information and hanged up.
Hello Ihar, it seems you have configured dynlist as a global overlay. I would note that not many overlays fully support this type of configuration at the moment and might not function correctly.
It is possible that dynlist will do just fine for your use case. Make sure you test with a simpler scenario as well (where databases are not subordinate and/or without back-meta in the picture) to see if there might be interaction between them.
Do let us know if you decide to investigate further and find a minimal use case where things start to break. Also a full test script that sets up a self-contained environment and reliably triggers the issue would greatly improve our chances of diagnosing it correctly.
Thanks,