[rabbitmq-discuss] Error in Rabbitmq 3.3.1 and Node getting down frequently..

Rohit Mukherjee rohitmukherjee26 at gmail.com
Thu May 29 04:58:22 BST 2014


Someone Please help me to get rid of this occassionally a node getting
down, although rabbitmq service is running fine

-Rohit


On Wed, May 28, 2014 at 10:46 PM, Rohit Mukherjee <
rohitmukherjee26 at gmail.com> wrote:

> Please Note , We have Both Node Running in Same AZ in EC2, and observed
> Network Partition...
>
>
> On Wed, May 28, 2014 at 10:45 PM, Rohit Mukherjee <
> rohitmukherjee26 at gmail.com> wrote:
>
>> Full Error Report :
>>
>> =ERROR REPORT==== 28-May-2014::14:41:36 ===
>> ** Generic server <0.191.0> terminating
>> ** Last message in was {mnesia_locker,'rabbit at vpc-prod-rabbitmq01
>> ',granted}
>> ** When Server state == undefined
>> ** Reason for termination ==
>> ** {unexpected_info,{mnesia_locker,'rabbit at vpc-prod-rabbitmq01',granted}}
>>
>> =ERROR REPORT==== 28-May-2014::14:41:36 ===
>> ** Generic server <0.194.0> terminating
>> ** Last message in was {mnesia_locker,'rabbit at vpc-prod-rabbitmq01
>> ',granted}
>> ** When Server state == undefined
>> ** Reason for termination ==
>> ** {unexpected_info,{mnesia_locker,'rabbit at vpc-prod-rabbitmq01',granted}}
>>
>> =ERROR REPORT==== 28-May-2014::14:41:36 ===
>> ** Generic server <0.192.0> terminating
>> ** Last message in was {mnesia_locker,'rabbit at vpc-prod-rabbitmq01',
>>                         {not_granted,
>>                          {cyclic,'rabbit at vpc-prod-rabbitmq01',
>>                           {gm_group,
>>
>>  {resource,<<"/">>,queue,<<"impression_click_es">>}},
>>                           write,write,
>>                           {tid,1215,<7209.30767.61>}}}}
>> ** When Server state == undefined
>> ** Reason for termination ==
>> ** {unexpected_info,
>>        {mnesia_locker,'rabbit at vpc-prod-rabbitmq01',
>>            {not_granted,
>>                {cyclic,'rabbit at vpc-prod-rabbitmq01',
>>                    {gm_group,
>>
>>  {resource,<<"/">>,queue,<<"impression_click_es">>}},
>>                    write,write,
>>                    {tid,1215,<7209.30767.61>}}}}}
>>
>> =ERROR REPORT==== 28-May-2014::14:41:36 ===
>> ** Generic server <0.193.0> terminating
>> ** Last message in was {mnesia_locker,'rabbit at vpc-prod-rabbitmq01
>> ',granted}
>> ** When Server state == undefined
>> ** Reason for termination ==
>> ** {unexpected_info,{mnesia_locker,'rabbit at vpc-prod-rabbitmq01',granted}}
>>
>>
>>
>> On Wed, May 28, 2014 at 10:42 PM, Rohit Mukherjee <
>> rohitmukherjee26 at gmail.com> wrote:
>>
>>> Hi ALL,
>>>
>>> We are seeing node getting down and seeing 3 Similar Error Always..
>>>
>>> 1)
>>>  =ERROR REPORT==== 28-May-2014::14:31:49 ===
>>> AMQP connection <0.6576.0> (running), channel 0 - error:
>>> {amqp_error,connection_forced,
>>>             "broker forced connection closure with reason
>>> 'shutdown'",none}
>>>
>>> 2)
>>>
>>> [10:39:58 PM] rohit mukherjee: Mirrored queue 'req_resp_es' in vhost
>>> '/': Slave <rabbit at vpc-prod-rabbitmq02.1.256.0> saw deaths of mirrors
>>> <rabbit at vpc-prod-rabbitmq01.2.29560.57>
>>>
>>>
>>>  3)
>>>  =ERROR REPORT==== 28-May-2014::14:31:51 ===
>>> Mnesia('rabbit at vpc-prod-rabbitmq02'): ** ERROR ** mnesia_event got
>>> {inconsistent_database, starting_partitioned_network,
>>> 'rabbit at vpc-prod-rabbitmq01'}
>>>
>>> Please Suggest Solution for the same
>>>
>>> Regards,
>>> Rohit
>>>
>>>
>>> On Thu, May 22, 2014 at 6:40 PM, Rohit Mukherjee <
>>> rohitmukherjee26 at gmail.com> wrote:
>>>
>>>> HI Team,
>>>>
>>>>
>>>>
>>>> RabbitMQ nodes are getting shutdown automatically , Can you please
>>>> suggest how should I fix the issue ..Please find the Log Strace Below
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =INFO REPORT==== 22-May-2014::09:43:12 ===
>>>>
>>>> Mirrored queue 'win_es' in vhost '/': Promoting slave
>>>> <rabbit at vpc-prod-rabbitmq02.1.10232.0> to master
>>>>
>>>>
>>>>
>>>> =INFO REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> Stopping RabbitMQ
>>>>
>>>>
>>>>
>>>> =INFO REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> stopped TCP Listener on [::]:5672
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10638.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10358.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10524.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10355.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10387.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10352.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10384.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10463.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10349.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10381.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10493.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =ERROR REPORT==== 22-May-2014::09:58:07 ===
>>>>
>>>> AMQP connection <0.10346.0> (running), channel 0 - error:
>>>>
>>>> {amqp_error,connection_forced,
>>>>
>>>>             "broker forced connection closure with reason
>>>> 'shutdown'",none}
>>>>
>>>>
>>>>
>>>> =INFO REPORT==== 22-May-2014::09:58:08 ===
>>>>
>>>> Halting Erlang VM
>>>>
>>>>
>>>>
>>>> =====
>>>> Regards,
>>>> Rohit Mukherjee
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Rohit Mukherjee
>>>
>>>
>>
>>
>> --
>> Regards,
>> Rohit Mukherjee
>>
>>
>
>
> --
> Regards,
> Rohit Mukherjee
>
>


-- 
Regards,
Rohit Mukherjee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140529/ae1d5bf1/attachment.html>


More information about the rabbitmq-discuss mailing list