Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1434822

Summary: rabbitmq got crashed multiple times
Product: Red Hat OpenStack Reporter: VIKRANT <vaggarwa>
Component: rabbitmq-serverAssignee: Peter Lemenkov <plemenko>
Status: CLOSED DUPLICATE QA Contact: Udi Shkalim <ushkalim>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: apevec, jeckersb, lhh, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rabbitmq-server-3.3.5-25.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-22 13:26:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description VIKRANT 2017-03-22 12:25:22 UTC 
Description of problem:

rabbitmq got crashed multiple times due to which instances were not able to reach the metadata.

Version-Release number of selected component (if applicable):

RHEL OSP 8 

$ awk '/rabbitmq/ {print $1}' installed-rpms 
rabbitmq-server-3.3.5-23.el7ost.noarch

How reproducible:
Not reproducible at desire. 

Steps to Reproduce:
1.  
2.
3.

Actual results:
rabbitmq got crash. 


Expected results:
rabbitmq should not get crash. 

Additional info:

From controller2 sosreport. 

~~~
=CRASH REPORT==== 1-Mar-2017::09:35:18 ===
  crasher:
    initial call: gen:init_it/6
    pid: <0.6624.0>
    registered_name: []
    exception exit: {undef,
                        [{rabbit_misc,get_env,
                             [rabbit,slave_wait_timeout,15000],
                             []},
                         {rabbit_mirror_queue_master,
                             promote_backing_queue_state,8,
                             [{file,"src/rabbit_mirror_queue_master.erl"},
                              {line,452}]},
                         {rabbit_mirror_queue_slave,promote_me,2,
                             [{file,"src/rabbit_mirror_queue_slave.erl"},
                              {line,615}]},
                         {rabbit_mirror_queue_slave,handle_call,3,
                             [{file,"src/rabbit_mirror_queue_slave.erl"},
                              {line,220}]},
                         {gen_server2,handle_msg,2,
                             [{file,"src/gen_server2.erl"},{line,1001}]},
                         {proc_lib,wake_up,3,
                             [{file,"proc_lib.erl"},{line,249}]}]}
      in function  gen_server2:terminate/3 (src/gen_server2.erl, line 1133)
    ancestors: [rabbit_mirror_queue_slave_sup,rabbit_sup,<0.674.0>]
    messages: [{'$gen_cast',policy_changed}]
    links: [<0.869.0>,<0.8320.2>]
    dictionary: [{process_name,
                      {rabbit_mirror_queue_slave,
                          {resource,<<"/">>,queue,
                              <<"q-plugin_fanout_b5a87f81b3ea45529659c70a62a11f15">>}}},
                  {guid,{{3009054393,1952830405,2332123253,2932299199},0}}]
    trap_exit: true
    status: running
    heap_size: 2586
    stack_size: 27
    reductions: 3798
  neighbours:
    neighbour: [{pid,<0.6625.0>},
                  {registered_name,[]},
                  {initial_call,
                      {gen,init_it,
                          ['Argument__1','Argument__2','Argument__3',
                           'Argument__4','Argument__5','Argument__6']}},
                  {current_function,{gen_server2,process_next_msg,1}},
                  {ancestors,
                      [<0.6624.0>,rabbit_mirror_queue_slave_sup,rabbit_sup,
                       <0.674.0>]},
                  {messages,[]},
                  {links,[<0.8320.2>]},
                  {dictionary,
                      [{random_seed,{12467,16901,24955}},
                       {process_name,
                           {gm,{resource,<<"/">>,queue,
                                   <<"q-plugin_fanout_b5a87f81b3ea45529659c70a62a11f15">>}}}]},
                  {trap_exit,false},
                  {status,waiting},
                  {heap_size,987},
                  {stack_size,7},
                  {reductions,3209}]
    neighbour: [{pid,<0.8320.2>},
                  {registered_name,[]},
                  {initial_call,
                      {gen,init_it,
                          ['Argument__1','Argument__2','Argument__3',
                           'Argument__4','Argument__5','Argument__6']}},
                  {current_function,{gen_server2,process_next_msg,1}},
                  {ancestors,
                      [<0.6624.0>,rabbit_mirror_queue_slave_sup,rabbit_sup,
                       <0.674.0>]},
                  {messages,[]},
                  {links,[<0.6624.0>,<0.6625.0>]},
                  {dictionary,
                      [{process_name,
                           {rabbit_mirror_queue_coordinator,
                               {resource,<<"/">>,queue,
                                   <<"q-plugin_fanout_b5a87f81b3ea45529659c70a62a11f15">>}}}]},
                  {trap_exit,false},
                  {status,waiting},
                  {heap_size,233},
                  {stack_size,7},
                  {reductions,92}]

~~~
Comment 5 Peter Lemenkov 2017-03-22 13:26:06 UTC 
Not sure about DHCP messages, but this RabbitMQ crash is a known issue. See bug 1370082 for further details and a fixed build.

In short - please upgrade to rabbitmq-server-3.3.5-25.el7ost.(or better to the latest build available). This will prevent RabbitMQ from crashing like this.

*** This bug has been marked as a duplicate of bug 1370082 ***