[erlang-questions] Unable to start ejabberd or use TCP/IP communication in erlang interpreter

[Kenneth Lundin]

Hi,

In order to be able to find out the reason for this problem that has
been around for quite some time now I would like you to do the
following on the machine where the problem occurs:

Start a Erlang node plain non distributed Erlang node and perform the
following in the shell:

dbg:tracer().
dbg:p(all,c).
dbg:tp(inet,dbg:fun2ms(fun(_)->return_trace() end)).
dbg:tp(prim_inet,dbg:fun2ms(fun(_)->return_trace() end)).
dbg:tp(inet_config,dbg:fun2ms(fun(_)->return_trace() end)).

% then try gen_tcp:listen as before

gen_tcp:listen(0,[]).

% You will get some trace printouts in the shell that I would like to see.
% from these we will hopefully be able to locate or at least get closer to the
% actual problem

Regards Kenneth (Product Responsible for Erlang/OTP at Ericsson)

On 12/26/06, Mikle <sign1024_3@REDACTED> wrote:
> I am try to learn Erlang language, but have some problems.
>
> When I start ejabberd server I receive a lot of error message
> then begins from
>
> {error_logger,{{2006,12,26},{17,16,43}},'Protocol: ~p: register/listen error: ~p
> ~n',[inet_tcp,enotsock]}
>
> In some conference I find a recomendation to check than TCP/IP functions
> properly.
> I execute gen_tcp:listen(0,[]). command in erlang interpreter and receive an
> error result.
>
> Eshell V5.5.2  (abort with ^G)
> 1> gen_tcp:listen(0,[]).
> {error,enotsock}
> 2>
>
> I have installed the latest version of Erlang.
> The computer functioning properly.
> All other programmes than use TCP/IP are working.
>
> What can I do to run Erlang properly?
> How to troubleshoot this problem?
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>