<div class="gmail_quote">On Thu, Jan 20, 2011 at 12:56 PM, Jerry Kuch <span dir="ltr"><<a href="mailto:jerryk@vmware.com">jerryk@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> ps -ax reveals that epmd is in fact running. �I googled even harder<br>
> after mailing the list and have also seen that it appears to be<br>
> related to erlang (epmd specifically) for the exact problem you are<br>
> talking about.<br>
><br>
> I killed epmd and started it up in debugging mode<br>
> (epmd -d -d -d) and then issued the requested command line, erl<br>
> -name bogusnode<br>
><br>
</div><div class="im">> the command line reported the following:<br>
> [jlh@hydra ~]$ erl -name bogusnode<br>
> {error_logger,{{2011,1,19},{22,46,41}},"Protocol: ~p: register<br>
> error:<br>
> ~p~n",["inet_tcp",{{badmatch,{error,epmd_close}},[{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}]}]}<br>
</div><div class="im">> Crash dump was written to: erl_crash.dump Kernel pid terminated<br>
> (application_controller)<br>
> ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})<br>
><br>
> Which is the same type of error, badmatch,{error,epmd_close} as when<br>
> I try to start RabbitMQ<br>
><br>
> I'll start following up on the erlang<br>
> forums, I'd rather not start off using an old version of erlang.<br>
><br>
> Thank you so much for getting me pointed in the proper direction!<br>
<br>
</div>Hi, Jeff...<br>
<br>
Glad it helped get you make some headway, and sorry you've had trouble.<br>
<br>
BTW, if you wouldn't mind copying this list with your results, whether<br>
from applying the aforementioned patch to a built-from-source Erlang<br>
of your own, or upgrading to a specific newer one that already<br>
incorporates it (if such a thing currently exists---I'm not sure it<br>
does yet), that would be great. �That way there's a Google-able record<br>
of the problem and a solution for other folks who may encounter it to<br>
come across...<br>
<br>
Best regards,<br>
<font color="#888888">Jerry<br>
</font></blockquote></div>I emailed the maintainer for the FreeBSD port but haven't heard back from them as yet. �For now, I've implemented the work around @�<meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://erlang.2086793.n4.nabble.com/crash-dump-at-ejabberd-startup-td3044533.html">http://erlang.2086793.n4.nabble.com/crash-dump-at-ejabberd-startup-td3044533.html</a>�.. �However, I wouldn't call this a "patch" as the current FreeBSD port is suppose to recognize a connection from an ip that matches the local ip, as being a true "Local". �<div>
<br></div><div>I'll follow up on this post when I hear back from the official port maintainer. �</div><div><br></div><div>Best,</div><div><br></div><div>Jeff</div>