Hi,
I use Ejabberd 1.1.2 and LDAP authentication against AD.
Sometimes Ejabberd stops to authenticate and to route messages (they went out but never reach a destination).
When trying to connect, in logs I see only "Accepted SSL connection" lines never followed by "Accepted legacy authentication for ...". And client says me "Connecting..." and nothing more happen.
What's can it be?
PS: Sorry for my poor english.
Re: ejabberd acts strangely
When trying to connect, in logs I see only "Accepted SSL connection" lines never followed by "Accepted legacy authentication for ...". And client says me "Connecting..." and nothing more happen.
Do you see any error messages in the logs?
No i don't. Only "Accepted
No i don't. Only "Accepted SSL connection ..." line by line.
Perhaps this problem is concerned with network timeouts between Ejabberd server and LDAP server, may it be so? But what about messages loss?
Alexey says: "yes, it can be
Alexey says: "yes, it can be because of ldap connection"
--
sander
Ok, but what's relation
Ok, but what's relation between bad LDAP connection and messages loss?
No, idea: better join the
No, idea: better join the ejabberd room and ask aleksey when he's online. Or try to post a message to the mailing list.
--
sander