> Am 01.06.2022 um 12:37 schrieb David Ritenour <d.riten...@martinfed.com>: > > Rainer, > > The directory's access log may provide you with the information you need to > resolve the issue. Grep for the originating IP or bindDN, then grep for the > connection number (conn=xxxxx) within the results. The output from the > second grep should provide the entire sequence of events for that connection, > including the connection, bind, operations, unbind, and the results for each > including success and failure ldap error codes. The op=x field within the > output indicates the operation order. > > Hope that helps.
Thanks, it turns out that after rebooting (or restarting) the app-server (which is within the real of the customer and outside my control), it started to work again. So, in the end it was a typical much-ado-about-nothing situation. I am sorry for the noise. Regards Rainer _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
