Stack trace of the error_logger process (PID <0.4.0>) shows,
among other things:
{<0.20.0>,"Protocol: ~p: register error: ~p~n",
["inet_tcp",
{{badmatch,{error,duplicate_name}},
[{inet_tcp_dist,listen,1},
{net_kernel,start_protos,4},
{net_kernel,start_protos,3},
{net_kernel,init_node,2},
{net_kernel,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}]}}}]}
which is a typical problem [1] caused by a "wedged" instance of ejabberd
running (or a epmd daemon thinking it's running).
So the question: does this same thing occur after a clean boot?
Rebooting the server isn't necessary, just make sure there's no beam,
beam.smp and epmd processes running.
You can find them like this:
# ps axc|grep beam
# ps axc|grep epmd
1. http://www.ejabberd.im/error/duplicate_name
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
