Hi,
I've been running an ejabberd cluster on 2.0beta1 on Amazon's ec2, and I'm using the new muc clustering feature. The ejabberd cluster is behind an haproxy instance with the haproxy connecting to it as a heartbeat check every second.
After about a day, I started getting many errors on both my ejabberd nodes all like the following, and I wasn't able to connect to the nodes.
Excerpt from ejabberd.log
849271 =ERROR REPORT==== 2008-01-14 18:50:18 ===
849272 ** Generic server <0.21636.10> terminating
849273 ** Last message in was {become_controller,<0.21637.10>}
849274 ** When Server state == {state,#Port<0.1986190>,
849275 gen_tcp,
849276 none,
849277 undefined,
849278 65536,
849279 undefined,
849280 infinity}
849281 ** Reason for termination ==
849282 ** {function_clause,[{xml_stream,close,[undefined]},
849283 {ejabberd_receiver,terminate,2},
849284 {gen_server,terminate,6},
849285 {proc_lib,init_p,5}]}
I'm new to ejabberd and erlang, so any help would be appreciated. I also tried updating to the last revision in svn today, but the changes don't seem to affect the files generating the error.
Thanks,
Don
