#78: c2s crash
---------------------+------------------------------------------------------
Reporter: tofu | Owner: smoku
Type: defect | Status: new
Priority: critical | Component: c2s
Version: 2.1 | Resolution:
Keywords: | Blocking:
---------------------+------------------------------------------------------
Comment (by jack):
We just had another one of these tonight. This is the only weird thing in
the log:
Mon Aug 6 23:07:31 2007 [notice] [98]
[EMAIL PROTECTED]/watch_arbiter] write error: Broken pipe (32)
Looking at the previous crashes in the logs there is one of these lines
before every one with this backtrace. There are other instances of Broken
pipe errors from regular users, but these don't seem to crash the server.
A first guess is that this may be related to legacy auth (since our normal
clients use sasl and the latency tester doesn't).
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/78#comment:18>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
Jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
