LDAP server treated as down due to wrong error returned than expected? about emqx HOT 5 OPEN

Thank you @JJGadgets for reporting it.
We'll fix it in 5.8.0

from emqx.

@JJGadgets @zmstone
I'm not sure I understood the question clearly, in fact here the result is not expected to be {error, invalidDNSyntax/timeout}, anything other than {error, ladp_closed} is considered alive.

from emqx.

@JJGadgets @zmstone I'm not sure I understood the question clearly, in fact here the result is not expected to be {error, invalidDNSyntax/timeout}, anything other than {error, ladp_closed} is considered alive.

Right. I did not take close enough look. Sorry.
I guess we need more clarification from @JJGadgets

from emqx.

@lafirest @zmstone if that's the case, what would you reckon is causing EMQX to treat the glauth server as offline?

That error returned of insufficientAccessRights by glauth is not ldap_closed either, yet it's not treated as up, which was what prompted me to check the code base where I found the invalidDNSyntax stuff.

(Although, I'm not a programmer, so I'm really going off my best guess here)

from emqx.

In the shared logs, there are alarm deactivation warnings following insufficientAccessRights

there isn’t alarm activation log.
maybe try looking for older logs.

from emqx.