https://bz.apache.org/bugzilla/show_bug.cgi?id=60923
--- Comment #5 from Guido W. <[email protected]> --- (In reply to Eric Covener from comment #4) > Perhaps you could log in the client SDK itself? I'm sorry, I won't be able to do that. So you are saying the ldap module logs [Tue Feb 28 12:54:36.457546 2017] [authnz_ldap:info] [pid 38022:tid 139731039868672] [client 10.10.10.56:38730] AH01695: auth_ldap authenticate: user svnuser1 authentication failed; URI /svn/asc091/Components/System_Tests/trunk [ldap_search_ext_s() for user failed][Administrative limit exceeded] because it got exactly that from the SDK: "Administrative limit exceeded"? If that is so, then maybe it's possible to check the connection state at that moment and if it's closed log that information too? Thanks, Guido > (In reply to Guido W. from comment #3) > > (In reply to Eric Covener from comment #2) > > > (In reply to Guido W. from comment #1) > > > > Addendum > > > > > > > > > > > > Suggested Fix: > > > > -------------- > > > > 3) Please don't use the error message "Administrative limit exceeded", > > > > because it is misleading in this case. > > > > > > Unless something unique is happening here, this generally come from the > > > SDK. > > > In what cases should it be second-guessed? > > > > That would imply that the response actually came from the LDAP server, but I > > don't think that is the case here, because the failed request is not logged > > at the LDAP server (not even at debug level). > > Perhaps you could log in the client SDK itself? Everything mod_ldap knows > about the backend LDAP server is via the calls to the LDAP SDK. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
