[ejabberd] constant "crashes" of ejabberd

Evgeniy Khramtsov xramtsov at gmail.com
Thu Oct 22 14:30:52 MSD 2009


Stephan Maihöfer wrote:
> hi,
>
> our servers keep on "crashing" with this error message
> A LOT. it seems that it does not affect the general running
> of the server, but i can't make out the cause of this,
> any ideas:
>
> =CRASH REPORT==== 22-Oct-2009::00:00:00 ===
>    crasher:
>      pid: <0.23112.100>
>      registered_name: []
>      exception exit: {function_clause,
>                          [{ejabberd_c2s,is_ip_blacklisted,[undefined]},
>                           {ejabberd_c2s,init,1},
>                           {gen_fsm,init_it,6},
>                           {proc_lib,init_p,5}]}
>        in function  gen_fsm:init_it/6
>      initial call: gen:init_it(gen_fsm,<0.234.0>,<0.234.0>,ejabberd_c2s,
>                                [{ejabberd_socket,
>                                     {socket_state,gen_tcp,#Port<0.1600518>,
>                                         <0.23111.100>}},
>                                 [inet,
>                                  {certfile,"/opt/ejabberd/server.pem"},
>                                  starttls,
>                                  {access,c2s},
>                                  {shaper,c2s_shaper},
>                                  {max_stanza_size,65536},
>                                  {ip,{0,0,0,0}}]],
>                                [])
>      ancestors: [ejabberd_c2s_sup,ejabberd_sup,<0.38.0>]
>      messages: []
>      links: [<0.234.0>]
>      dictionary: []
>      trap_exit: false
>      status: running
>      heap_size: 610
>      stack_size: 23
>      reductions: 148
>    neighbours:
>   

That bug was fixed in r2155 (2009-06-12). You should update ejabberd.

-- 
Regards,
Evgeniy Khramtsov, ProcessOne.
xmpp:xram at jabber.ru.



More information about the ejabberd mailing list