ejabberd - Comments for "TLS Error in Logs" https://www.ejabberd.im/node/2828 en Re: tls error https://www.ejabberd.im/node/2828#comment-51808 <p>I think I'm seeing the same thing. I get the following error around 10 times per day. The only issues that I am aware of are related to s2s presence packets to/from google talk users.</p> <pre> =CRASH REPORT==== 15-Feb-2008::08:02:00 === crasher: pid: &lt;0.14393.1&gt; registered_name: [] error_info: {badarg,[{erlang,port_control, [#Port&lt;0.52123&gt;, 3, &lt;&lt;21,3,1,0,24,104,191,171,1,248,218,49,93, 111,12,26,152,168,77,60,19,209,137,150, 12,241,70,41,229&gt;&gt;]}, {tls,recv_data,2}, {ejabberd_receiver,handle_info,2}, {gen_server,handle_msg,6}, {proc_lib,init_p,5}]} initial_call: {gen,init_it, [gen_server, &lt;0.23969.0&gt;, &lt;0.23969.0&gt;, ejabberd_receiver, [#Port&lt;0.52121&gt;,gen_tcp,none,65536,&lt;0.14392.1&gt;], []]} ancestors: [ejabberd_receiver_sup,ejabberd_sup,&lt;0.23811.0&gt;] messages: [{'$gen_cast',close}] links: [&lt;0.23969.0&gt;] dictionary: [] trap_exit: false status: running heap_size: 1597 stack_size: 21 reductions: 7102 neighbours: =SUPERVISOR REPORT==== 15-Feb-2008::08:02:00 === Supervisor: {local,ejabberd_receiver_sup} Context: child_terminated Reason: {badarg,[{erlang,port_control, [#Port&lt;0.52123&gt;, 3, &lt;&lt;21,3,1,0,24,104,191,171,1,248,218,49,93, 111,12,26,152,168,77,60,19,209,137,150, 12,241,70,41,229&gt;&gt;]}, {tls,recv_data,2}, {ejabberd_receiver,handle_info,2}, {gen_server,handle_msg,6}, {proc_lib,init_p,5}]} Offender: [{pid,&lt;0.14393.1&gt;}, {name,undefined}, {mfa, {ejabberd_receiver, start_link, [#Port&lt;0.52121&gt;,gen_tcp,none,65536,&lt;0.14392.1&gt;]}}, {restart_type,temporary}, {shutdown,brutal_kill}, {child_type,worker}] </pre> Fri, 15 Feb 2008 21:15:28 +0000 zjt comment 51808 at https://www.ejabberd.im