[rabbitmq-discuss] rabbitmq_mochiweb timeout fix is in rabbitmq 2.7.1?

Wed Mar 13 11:10:50 GMT 2013

That fix is in 2.7.1 (and indeed all versions >= 2.6.0) but you're not 
seeing that problem - you are getting eaddrinuse, i.e. the port is 
already taken.

Later versions of RabbitMQ than 2.7.1 report this error in a more 
readable way :-)

Cheers, Simon

On 13/03/13 09:59, Rosa, Andrea (HP Cloud Services) wrote:
> Hi all,
>
> Sometime I get errors (reported at the bottom of this message) and, browsing the mailing list archive, I found that a possibly cause for that is when mochiweb takes more than 5 seconds to start.
> That appeared in the 2.5.1 version and there was a fix proposed for it:
>
> http://www.rabbitmq.com/releases/plugins/v2.5.1/rabbitmq_mochiweb-2.5.1-registry-timeout-fix.ez
> is that fix included in the 2.7.1 version?
> That error happens to me when I run "service rabbitmq-server restart" command  2 -3 times in a row, but unfortunately I am not able to reproduce it.
>
> Regards
> --
> Andrea Rosa
>
>
> =ERROR REPORT==== 11-Feb-2013::15:44:13 ===
> ** Generic server rabbit_mochiweb_registry terminating
> ** Last message in was {add,rabbit_mgmt,#Fun<rabbit_mochiweb.2.75707079>,
>                              #Fun<rabbit_mochiweb.0.51174676>,
>                              {[],"RabbitMQ Management"}}
> ** When Server state == undefined
> ** Reason for termination ==
> ** {{case_clause,
>          {error,
>              {eaddrinuse,
>                  {child,undefined,
>                      {rabbit_mochiweb_web,mgmt},
>                      {rabbit_mochiweb_web,start,[{mgmt,[{port,55672}]}]},
>                      transient,5000,worker,dynamic}}}},
>      [{rabbit_mochiweb_sup,ensure_listener,1},
>       {rabbit_mochiweb_registry,handle_call,3},
>       {gen_server,handle_msg,5},
>       {proc_lib,init_p_do_apply,3}]}
>
> =INFO REPORT==== 11-Feb-2013::15:44:13 ===
>      application: rabbitmq_management
>      exited: {bad_return,
>               {{rabbit_mgmt_app,start,[normal,[]]},
>                {'EXIT',
>                 {{{case_clause,
>                    {error,
>                     {eaddrinuse,
>                      {child,undefined,
>                       {rabbit_mochiweb_web,mgmt},
>                       {rabbit_mochiweb_web,start,[{mgmt,[{port,55672}]}]},
>                       transient,5000,worker,dynamic}}}},
>                   [{rabbit_mochiweb_sup,ensure_listener,1},
>                    {rabbit_mochiweb_registry,handle_call,3},
>                    {gen_server,handle_msg,5},
>                    {proc_lib,init_p_do_apply,3}]},
>                  {gen_server,call,
>                   [rabbit_mochiweb_registry,
>                    {add,rabbit_mgmt,#Fun<rabbit_mochiweb.2.75707079>,
>                     #Fun<rabbit_mochiweb.0.51174676>,
>                     {[],"RabbitMQ Management"}},
>                    infinity]}}}}}
>      type: permanent
>
>
> from sasl log
> =CRASH REPORT==== 11-Feb-2013::16:45:27 ===
>    crasher:
>      initial call: rabbit_mochiweb_registry:init/1
>      pid: <0.2051.0>
>      registered_name: []
>      exception exit: {timeout,
>                          {gen_server,call,
>                              [application_controller,
>                               {set_env,rabbitmq_mochiweb,
>                                   {dispatch,'*'},
>                                   {[],
>                                    #Fun<rabbit_mochiweb_registry.0.32312211>}}]}}
>        in function  gen_server:init_it/6
>      ancestors: [rabbit_mochiweb_sup,<0.133.0>]
>      messages: []
>      links: [<0.134.0>]
>      dictionary: []
>      trap_exit: false
>      status: running
>      heap_size: 377
>      stack_size: 24
>      reductions: 115
>    neighbours:
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
Simon MacMullen
RabbitMQ, VMware