[erlang-questions] crash dump at ejabberd startup

Michael Santos michael.santos@REDACTED
Tue Nov 16 13:59:15 CET 2010

On Tue, Nov 16, 2010 at 11:14:01AM +0100, tom@REDACTED wrote:
> Hello everybody in the Erlang universe,
> I got stuck with a problem getting ejabberd to run in a FreeBSD8 Jail. 
> Erlang and ejabberd were built using the Ports Collection (this week).
> As far as I could learn from googling all this, the issue goes back to the 
> erlang environment and abviously has something to do with "inet", TCP etc.. 
> Well, even I know a bit about Unix I can't help myself with the error 
> messages erlang spits out (no clue what these messages actually / precisely 
> want to tell me):
> ejabberd Start:
> # ejabberdctl status
> {error_logger,{{2010,11,16},{9,56,20}},"Protocol: ~p: register error: ~p~n",
> ["inet_tcp",{{badmatch,{error,epmd_close}},[{inet_tcp_dist,listen,1},

When a distributed Erlang node starts up, it attempts to register itself
with an epmd daemon listening on localhost on port 4369 and starts one,
if an epmd is not running.

Check epmd is running and if the node is allowed to contact it from the
jail. You can get debugging info by running epmd manually: epmd -d -d -d

More information about the erlang-questions mailing list