ejabberd - Comments for "s2s stop work after upgrade to ejabberd 2.1-RC2" https://www.ejabberd.im/node/3714 en > Any "side effects" of this https://www.ejabberd.im/node/3714#comment-54799 <p>&gt; Any "side effects" of this patch ?</p> <p>No. This patch doesn't have bad effects. If S2S works well for you, you can continue until new version is published.</p> <p>&gt; If ejabberd compiled with "new" version Erlang/OTP it work without this patch ? </p> <p>Right. You can have:</p> <ul> <li>ejabberd 2.1.0-rc2 + patch, compiled with Erlang/OTP R12B-5 or older </li><li>ejabberd 2.1.0-rc2, compiled with Erlang/OTP R13B or newer </li></ul> Thu, 22 Oct 2009 14:40:19 +0000 mfoss comment 54799 at https://www.ejabberd.im thaks! https://www.ejabberd.im/node/3714#comment-54795 <p>s2s work now. If ejabberd compiled with "new" version Erlang/OTP it work without this patch ? Any "side effects" of this patch ?</p> Thu, 22 Oct 2009 06:34:59 +0000 evadim comment 54795 at https://www.ejabberd.im Try this small fix https://www.ejabberd.im/node/3714#comment-54792 <p>I found the problem. It affects s2s out connections in ejabberd 2.1.0-rc2 when using Erlang/OTP R12 or older.</p> <p>You can fix easily, only need to remove one line:</p> <pre>--- src/ejabberd_s2s_out.erl +++ src/ejabberd_s2s_out.erl @@ -272,7 +272,6 @@ open_socket2(Type, Addr, Port) -&gt; case (catch ejabberd_socket:connect(Addr, Port, [binary, {packet, 0}, {send_timeout, ?TCP_SEND_TIMEOUT}, - {send_timeout_close, true}, {active, false}, Type | SockOpts], Timeout)) of {ok, _Socket} = R -&gt; R; </pre><p> If you install rc2 again and you try this solution, please tell me if that solves the problem.</p> Wed, 21 Oct 2009 21:14:05 +0000 mfoss comment 54792 at https://www.ejabberd.im downgrade to RC1 solve this https://www.ejabberd.im/node/3714#comment-54791 <p>downgrade to RC1 solve this issue</p> Wed, 21 Oct 2009 20:15:13 +0000 evadim comment 54791 at https://www.ejabberd.im