Есть два домена и более
Если, по какой-либо причине, происходит падение канала между доменами, клиенты перестают видеть клиентов из другого домена, хотя в web-admin имеется исходящее s2s соединение (на серверах). Помогает, как правило ТОЛЬКО перезапуск одного из серверов с которым терялась связь. Связь между серверами шифруется/не шифруется. Клиенты JAJC 0.0.8.121, Psi 0.10 и Miranda IM 0.7.0
%% -------------------
There are two domains and more
If, on some reason, there is falling of channel between domains, clients stop to see clients from other domain, although there is outgoing s2s connection in web-admin (on servers). Helps, as a rule ONLY one restarting of servers which connection was lost with. Connection between the servers of shifruetsya/ne is coded. Clients of JAJC 0.0.8.121, Psi 0.10 and Miranda IM 0.7.0
Anybody answer my question?
Anybody answer my question?
K0NCTANT1N wrote:I very wait an answer
I very wait an answer
I don't understand what is
I don't understand what is the question exactly.
If two Jabber servers are connected using s2s, and for some reason their connection is broken, their users can't see online. If the connection was not closed properly, it may be difficult for the servers to establish a proper new s2s connection, because maybe one of the servers still thinks the old connection is good. In this case, it helps to restart the server.
Once the s2s connection is established again, maybe it is required that the clients login again, or update their presence, so their contacts in the other server see them online again.
badlop wrote:If the
If the connection was not closed properly, it may be difficult for the servers to establish a proper new s2s connection, because maybe one of the servers still thinks the old connection is good. In this case, it helps to restart the server.
How to avoid automatically such here the conflict (by mistake thinks a server, what s2s connection still is)? Each time to overload a server is not an output.
в Примечании
в Примечании к релизу ejabberd 2.0.0 rc1 говориться
* Server to Server (s2s)
- More robust code with connection timeout implementation.
...
- s2s retrial interval.
Возможно именно это и исправлено в новом релизе? т.к. мой тестовый сервер ejabberd 2.0.0 не наблюдает таких проблем, как в ejabberd 1.1.4
%% -------------------
in Release Notes ejabberd 2.0.0 rc1 talked
* Server to Server (s2s)
- More robust code with connection timeout implementation.
...
- s2s retrial interval.
Possibly exactly it and is it corrected in a new release? in fact my test server of ejabberd 2.0.0 does not look after such problems, as in ejabberd 1.1.4