I can start the daemon with ejabberdctl, but I don't recieve anything back when I telnet to the port 5222. Here's what's in the log files:
=ERROR REPORT==== 2010-10-29 19:49:22 ===
** Generic server <0.373.0> terminating
** Last message in was {tcp,#Port<0.3528>,
<<"">>}
** When Server state == {state,#Port<0.3528>,gen_tcp,none,<0.374.0>,65536,
{xml_stream_state,<0.374.0>,#Port<0.3529>,[],0,
65536},
infinity}
** Reason for termination ==
** {badarg,[{erlang,port_control,
[#Port<0.3529>,0,
<<"">>]},
{xml_stream,parse,2},
{ejabberd_receiver,process_data,2},
{ejabberd_receiver,handle_info,2},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]}
tried recompiling. new error
I get this error in the erlang log when connecting to the port:
=CRASH REPORT==== 29-Oct-2010::21:00:54 ===
crasher:
initial call: ejabberd_receiver:init/1
pid: <0.356.0>
registered_name: []
exception exit: {badarg,[{erlang,port_close,[#Port<0.3506>]},
{xml_stream,close,1},
{ejabberd_receiver,terminate,2},
{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}
in function gen_server:terminate/6
ancestors: [ejabberd_receiver_sup,ejabberd_sup,<0.36.0>]
messages: []
links: [#Port<0.3495>,<0.250.0>]
dictionary: []
trap_exit: false
status: running
heap_size: 233
stack_size: 24
reductions: 175
neighbours:
=SUPERVISOR REPORT==== 29-Oct-2010::21:00:54 ===
Supervisor: {local,ejabberd_receiver_sup}
Context: child_terminated
Reason: {badarg,[{erlang,port_close,[#Port<0.3506>]},
{xml_stream,close,1},
{ejabberd_receiver,terminate,2},
{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}
Offender: [{pid,<0.356.0>},
{name,undefined},
{mfargs,
{ejabberd_receiver,start_link,
[#Port<0.3495>,gen_tcp,none,65536]}},
{restart_type,temporary},
{shutdown,brutal_kill},
{child_type,worker}]
Check logs at ejabberd start
I get this error in the erlang log when connecting to the port:
Reason: {badarg,[{erlang,port_close,[#Port<0.3506>]},
The documentation of the function port_close says:
You can try to recompile ejabberd.
Also, look if there is any error in the log files related to ejabberd starting: maybe ejabberd reports a more useful error report when starting itself.