[ejabberd] lots of "noproc" errors in logfile

Stephan Maihöfer sma at turtle-entertainment.de
Fri Jan 15 17:56:46 MSK 2010


hi there,

when our jabber-cluster is under load, we see A LOT of the
errors attached to the end of the mail. it seems that it means
that ejabberd can not handle some certain action because the
client has disconnected in the meantime. and seems somehow
similar to this:

	https://support.process-one.net/browse/EJAB-403

as you can see we use http-bind and can not really guarantee
that users actually "close" their connections since that
would have to be onunload or something like that and thats
quite different in browser behaviour and all that.

am i right in my assumption and do we have to "care" about
these messages at all apart from them cloggin up logfiles?

thanks in advance,
stephan

MESSAGES:

Jan  5 16:34:34 node3 EJABBERD: =CRASH REPORT==== 5-Jan-2010::16:34:34 ===
Jan  5 16:34:34 node3 EJABBERD:   crasher:
Jan  5 16:34:34 node3 EJABBERD:     pid: <0.2186.0>
Jan  5 16:34:34 node3 EJABBERD:     registered_name: []
Jan  5 16:34:34 node3 EJABBERD:     exception exit: {noproc,
Jan  5 16:34:34 node3 EJABBERD:                         {gen_fsm,sync_send_all_state_event,
Jan  5 16:34:34 node3 EJABBERD:                             [<0.14837.0>,
Jan  5 16:34:34 node3 EJABBERD:                              {http_put,2535263041,
Jan  5 16:34:34 node3 EJABBERD:                                  [{"rid","2535263041"},
Jan  5 16:34:34 node3 EJABBERD:                                   {"xmlns",
Jan  5 16:34:34 node3 EJABBERD:                                    "http://jabber.org/protocol/httpbind"},
Jan  5 16:34:34 node3 EJABBERD:                                   {"sid",
Jan  5 16:34:34 node3 EJABBERD:                                    "f2ace5d5e97622ae2a7159d5838f9cb030df5e03"}],
Jan  5 16:34:34 node3 EJABBERD:                                  [],1,[],
Jan  5 16:34:34 node3 EJABBERD:                                  {{10,65,0,43},42985}}]}}
Jan  5 16:34:34 node3 EJABBERD:       in function  gen_fsm:sync_send_all_state_event/2
Jan  5 16:34:34 node3 EJABBERD:       in call from ejabberd_http_bind:http_put/6
Jan  5 16:34:34 node3 EJABBERD:       in call from ejabberd_http_bind:handle_http_put/6
Jan  5 16:34:34 node3 EJABBERD:       in call from ejabberd_http:process_request/1
Jan  5 16:34:34 node3 EJABBERD:       in call from ejabberd_http:process_header/2
Jan  5 16:34:34 node3 EJABBERD:       in call from ejabberd_http:receive_headers/1
Jan  5 16:34:34 node3 EJABBERD:     initial call: ejabberd_http:receive_headers({state,gen_tcp,#Port<0.4378>,
Jan  5 16:34:34 node3 EJABBERD:                                                  undefined,undefined,
Jan  5 16:34:34 node3 EJABBERD:                                                  undefined,undefined,
Jan  5 16:34:34 node3 EJABBERD:                                                  undefined,undefined,"en",
Jan  5 16:34:34 node3 EJABBERD:                                                  [{["admin"],
Jan  5 16:34:34 node3 EJABBERD:                                                    ejabberd_web_admin},
Jan  5 16:34:34 node3 EJABBERD:                                                   {["http-bind"],
Jan  5 16:34:34 node3 EJABBERD:                                                    mod_http_bind},
Jan  5 16:34:34 node3 EJABBERD:                                                   {["http-poll"],
Jan  5 16:34:34 node3 EJABBERD:                                                    ejabberd_http_poll}],
Jan  5 16:34:34 node3 EJABBERD:                                                  undefined,undefined,
Jan  5 16:34:34 node3 EJABBERD:                                                  undefined,[],false,[]})
Jan  5 16:34:34 node3 EJABBERD:     ancestors: [ejabberd_http_sup,ejabberd_sup,<0.38.0>]
Jan  5 16:34:34 node3 EJABBERD:     messages: []
Jan  5 16:34:34 node3 EJABBERD:     links: [<0.243.0>,#Port<0.4378>]
Jan  5 16:34:34 node3 EJABBERD:     dictionary: []
Jan  5 16:34:34 node3 EJABBERD:     trap_exit: false
Jan  5 16:34:34 node3 EJABBERD:     status: running
Jan  5 16:34:34 node3 EJABBERD:     heap_size: 4181
Jan  5 16:34:34 node3 EJABBERD:     stack_size: 23
Jan  5 16:34:34 node3 EJABBERD:     reductions: 1429
Jan  5 16:34:34 node3 EJABBERD:   neighbours:


More information about the ejabberd mailing list