Check logs at ejabberd start

mfoss — Tue, 02 Nov 2010 20:22:23 +0000

greg_nate wrote:

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:

port_close(Port) -> true
...
Failure: badarg if Port is not an open port or the registered name of an open port.

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.

tried recompiling. new error

greg_nate — Fri, 29 Oct 2010 20:02:34 +0000

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}]

ejabberd - Comments for "ejabberd compiles(X86_64) but doesn&#039;t work"

Check logs at ejabberd start

tried recompiling. new error

ejabberd - Comments for "ejabberd compiles(X86_64) but doesn't work"