[rabbitmq-discuss] Many errors in mirrored queues with rabbitmq 3.1.4

Thu Aug 15 10:20:47 BST 2013

Yes, this is a bug in 3.1.4 which we noticed yesterday. Very sorry about 
that. We will be pushing out a 3.1.5 ASAP to address this.

Cheers, Simon

On 15/08/13 04:06, Dan_b wrote:
> Hi
>
> We have a Centos 5 server with rabbitmq 3.1.4 and all the queues are
> mirrored to a Centos 6 server.  On the Centos6 server with the mirrored
> queues we are seeing many errors:
>
> =CRASH REPORT==== 15-Aug-2013::02:52:44 ===
>    crasher:
>      initial call: gen:init_it/7
>      pid: <0.710.0>
>      registered_name: delegate_4
>      exception exit: {{case_clause,{ok,{<0.1303.0>,#Ref<0.0.0.33680>}}},
>                       [{delegate,handle_info,2},
>                        {gen_server2,handle_msg,2},
>                        {proc_lib,wake_up,3}]}
>        in function  gen_server2:terminate/3
>      ancestors: [delegate_sup,rabbit_sup,<0.604.0>]
>      messages: []
>      links: [<0.705.0>]
>      dictionary: []
>      trap_exit: false
>      status: running
>      heap_size: 1597
>      stack_size: 24
>      reductions: 66062
>    neighbours:
>
> =SUPERVISOR REPORT==== 15-Aug-2013::02:52:44 ===
>       Supervisor: {local,delegate_sup}
>       Context:    child_terminated
>       Reason:     {{case_clause,{ok,{<0.1303.0>,#Ref<0.0.0.33680>}}},
>                    [{delegate,handle_info,2},
>                     {gen_server2,handle_msg,2},
>                     {proc_lib,wake_up,3}]}
>       Offender:   [{pid,<0.710.0>},
>                    {name,4},
>                    {mfargs,{delegate,start_link,[4]}},
>                    {restart_type,transient},
>                    {shutdown,4294967295},
>                    {child_type,worker}]
>
> The erlang version on Centos 6 is R14B-04.2 and on the Centos 5 box it is
> R14B-04.1.  We have an identical configuration in another data center but it
> is running rabbitmq 3.1.3 and there are no issues so I think it is related
> to the current version.  Any help would be greatly appreciated because as it
> stands we can't use it (the crashes are causing memory and cpu usage to be
> high when placed under load).
>
> Regards
> Dan
>
>
>
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Many-errors-in-mirrored-queues-with-rabbitmq-3-1-4-tp28801.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
Simon MacMullen
RabbitMQ, Pivotal