[rabbitmq-discuss] Having trouble installing on Ubuntu

Wed Mar 10 01:45:07 GMT 2010

Jason,

Jason Carver wrote:
> 
>     I've looked through the strace. There are definitely some dns lookups
>     going on there of what look to be IP addresses. This could be something
>     that's going wrong. There doesn't seem to be anything that stands out
>     yelling "this is what is going wrong".
> 
> As far as I know, the dns settings were left as default (Slicehost, 
> Ubuntu 9.10 Karmic).  Do I need to explicitly configure something to get 
> it working?

That should be fine. There are certainly plenty of rabbit users on 
karmic that haven't run into difficulties.

>     What happens if you just run "erl" from the command line, and what
>     happens if you just run "erl -sname rabbit" ?
> 
> 
> `erl` gives a standard-looking:
> Erlang R13B01 (erts-5.7.2) [source] [64-bit] [smp:4:4] [rq:4] 
> [async-threads:0] [kernel-poll:false]
> 
> Eshell V5.7.2  (abort with ^G)
> 1> q
> 
> 
> `erl -sname rabbit` gives:
> {error_logger,{{2010,3,9},{19,41,1}},"Protocol: ~p: register error: 
> ~p~n",["inet_tcp",{{badmatch,{error,etimedout}},[{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}]}]}
> {error_logger,{{2010,3,9},{19,41,1}},crash_report,[[{initial_call,{net_kernel,init,['Argument__1']}},{pid,<0.21.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},{ancestors,[net_sup,kernel_sup,<0.8.0>]},{messages,[]},{links,[#Port<0.51>,<0.18.0>]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,377},{stack_size,24},{reductions,444}],[]]}
> {error_logger,{{2010,3,9},{19,41,1}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[[rabbit,shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
> {error_logger,{{2010,3,9},{19,41,1}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid,undefined},{name,net_sup},{mfa,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
> {error_logger,{{2010,3,9},{19,41,1}},std_info,[{application,kernel},{exited,{shutdown,{kernel,start,[normal,[]]}}},{type,permanent}]}
> {"Kernel pid 
> terminated",application_controller,"{application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}}"}
> 
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller) 
> ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

That means the problem isn't with rabbit code, but some general erlang 
networking issue. As I mentioned earlier, we haven't seen this before 
ourselves.

I've done some googling and found this:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498068

Any use?

If not, would you mind posting the above observations to the 
erlang-questions mailing list? Or perhaps ask on #erlang.

Regards,

Matthias.