LDAP getting user operation failed and LDAP authenticate operation failed error messages

Hi ,

we have ROR for ES version 6.1.1 .
during the last few days we see some error messages in the ES logs .
those errors are once in two - three days .
during that time error messages appears in the application’s log.
I’ve done some checks and saw nothing special like high CPU or heap usage while those errors appears.
the error messages and the configuration are attached .
readonlyrest ldap errors.zip (2.6 KB) can you please advise ?

Thanks.

Copying the stack traces here for search engine users:


[2019-06-26T01:10:22,614][ERROR][t.b.r.a.b.d.l.i.UnboundidLdapAuthorizationService] [
ode_name] LDAP getting user operation failed.
tech.beshu.ror.acl.blocks.definitions.ldap.implementations.LdapUnexpectedResult: null
        at tech.beshu.ror.acl.blocks.definitions.ldap.implementations.BaseUnboundidLdapService.$anonfun$ldapUserBy$2(UnboundidLdapService.scala:232) ~[?:?]
        at monix.eval.internal.TaskRunLoop$.startFull(TaskRunLoop.scala:147) ~[?:?]
        at monix.eval.internal.TaskRestartCallback.syncOnSuccess(TaskRestartCallback.scala:108) ~[?:?]
        ...

--
2019-06-26T01:10:22,638][ERROR][t.b.r.a.b.Block          ] [
ode_name] allow all for GROUP_A: ldap_auth rule matching got an error null
tech.beshu.ror.acl.blocks.definitions.ldap.implementations.LdapUnexpectedResult: null
        at tech.beshu.ror.acl.blocks.definitions.ldap.implementations.BaseUnboundidLdapService.$anonfun$ldapUserBy$2(UnboundidLdapService.scala:232) ~[?:?]
        at monix.eval.internal.TaskRunLoop$.startFull(TaskRunLoop.scala:147) ~[?:?]
        at monix.eval.internal.TaskRestartCallback.syncOnSuccess(TaskRestartCallback.scala:108) ~[?:?]
        at monix.eval.internal.TaskRestartCallback$$anon$1.run(TaskRestartCallback.scala:128) ~[?:?]
        at monix.execution.internal.Trampoline.monix$execution$internal$Trampoline$$immediateLoop(Trampoline.scala:66) ~[?:?]
        at monix.execution.internal.Trampoline.startLoop(Trampoline.scala:32) ~[?:?]

This is in the works already (Jira ID RORDEV-66) more comment from @coutoPL?

thank you Simone .
do you know if it’s a matter of days or weeks until you fix it ?

Will wait on @coutoPL to confirm, but in a different post, that stack trace was symptomatic of a (temporary?) connection failure to the LDAP server. And the Jira issue is just about making that log less cryptic for the user.

We are about to release a new version, not sure if this fix is going to be part of it, but we can create a pre build for you as soon as we get it fixed.