I have a debian box running tasks with celery and rabbitmq for about a year. Recently I noticed tasks were not being processed so I logged into the system and noticed that celery could not connect to rabbitmq. I restarted rabbitmq-server and even though celery was not complaining anymore it was not executing new tasks now. The odd thing was that rabbitmq was devouring cpu and memory resources like crazy. Restarting server would not solve the problem. After spending couple hours looking for solution online to no avail I decided to rebuild the server.

I rebuilt new server with Debian 7.5, rabbitmq 2.8.4, celery 3.1.13 (Cipater). For about an hour or so everything worked beautifully again until celery started complaining again that it can&#39;t connect to rabbitmq!

    [2014-08-06 05:17:21,036: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
    Trying again in 6.00 seconds...

I restarted rabbitmq `service rabbitmq-server start` and same issue gain:

rabbitmq started again swelling up constantly pounding on cpu and slowly taking over all ram and swap:

    PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
    21823 rabbitmq  20   0  908m 488m 3900 S 731.2 49.4   9:44.74 beam.smp

Here&#39;s the result on `rabbitmqctl status`:

    Status of node &#39;rabbit@li370-61&#39; ...
    [{pid,21823},
     {running_applications,[{rabbit,&quot;RabbitMQ&quot;,&quot;2.8.4&quot;},
                            {os_mon,&quot;CPO  CXC 138 46&quot;,&quot;2.2.9&quot;},
                            {sasl,&quot;SASL  CXC 138 11&quot;,&quot;2.2.1&quot;},
                            {mnesia,&quot;MNESIA  CXC 138 12&quot;,&quot;4.7&quot;},
                            {stdlib,&quot;ERTS  CXC 138 10&quot;,&quot;1.18.1&quot;},
                            {kernel,&quot;ERTS  CXC 138 10&quot;,&quot;2.15.1&quot;}]},
     {os,{unix,linux}},
     {erlang_version,&quot;Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:8:8] [async-threads:30] [kernel-poll:true]\n&quot;},
     {memory,[{total,489341272},
              {processes,462841967},
              {processes_used,462685207},
              {system,26499305},
              {atom,504409},
              {atom_used,473810},
              {binary,98752},
              {code,11874771},
              {ets,6695040}]},
     {vm_memory_high_watermark,0.3999999992280962},
     {vm_memory_limit,414559436},
     {disk_free_limit,1000000000},
     {disk_free,48346546176},
     {file_descriptors,[{total_limit,924},
                        {total_used,924},
                        {sockets_limit,829},
                        {sockets_used,3}]},
     {processes,[{limit,1048576},{used,1354}]},
     {run_queue,0},

Some entries from /var/log/rabbitmq:

    =WARNING REPORT==== 8-Aug-2014::00:11:35 ===
    Mnesia(&#39;rabbit@li370-61&#39;): ** WARNING ** Mnesia is overloaded: {dump_log,
                                                                    write_threshold}
    
    =WARNING REPORT==== 8-Aug-2014::00:11:35 ===
    Mnesia(&#39;rabbit@li370-61&#39;): ** WARNING ** Mnesia is overloaded: {dump_log,
                                                                    write_threshold}
    
    =WARNING REPORT==== 8-Aug-2014::00:11:35 ===
    Mnesia(&#39;rabbit@li370-61&#39;): ** WARNING ** Mnesia is overloaded: {dump_log,
                                                                    write_threshold}
    
    =WARNING REPORT==== 8-Aug-2014::00:11:35 ===
    Mnesia(&#39;rabbit@li370-61&#39;): ** WARNING ** Mnesia is overloaded: {dump_log,
                                                                    write_threshold}
    
    =WARNING REPORT==== 8-Aug-2014::00:11:36 ===
    Mnesia(&#39;rabbit@li370-61&#39;): ** WARNING ** Mnesia is overloaded: {dump_log,
                                                                    write_threshold}
    
    =INFO REPORT==== 8-Aug-2014::00:11:36 ===
    vm_memory_high_watermark set. Memory used:422283840 allowed:414559436
    
    =WARNING REPORT==== 8-Aug-2014::00:11:36 ===
    memory resource limit alarm set on node &#39;rabbit@li370-61&#39;.
    
    **********************************************************
    *** Publishers will be blocked until this alarm clears ***
    **********************************************************
    
    =INFO REPORT==== 8-Aug-2014::00:11:43 ===
    started TCP Listener on [::]:5672
    
    =INFO REPORT==== 8-Aug-2014::00:11:44 ===
    vm_memory_high_watermark clear. Memory used:290424384 allowed:414559436
    
    =WARNING REPORT==== 8-Aug-2014::00:11:44 ===
    memory resource limit alarm cleared on node &#39;rabbit@li370-61&#39;
    
    =INFO REPORT==== 8-Aug-2014::00:11:59 ===
    vm_memory_high_watermark set. Memory used:414584504 allowed:414559436
    
    =WARNING REPORT==== 8-Aug-2014::00:11:59 ===
    memory resource limit alarm set on node &#39;rabbit@li370-61&#39;.
    
    **********************************************************
    *** Publishers will be blocked until this alarm clears ***
    **********************************************************
    
    =INFO REPORT==== 8-Aug-2014::00:12:00 ===
    vm_memory_high_watermark clear. Memory used:411143496 allowed:414559436
    
    =WARNING REPORT==== 8-Aug-2014::00:12:00 ===
    memory resource limit alarm cleared on node &#39;rabbit@li370-61&#39;
    
    =INFO REPORT==== 8-Aug-2014::00:12:01 ===
    vm_memory_high_watermark set. Memory used:415563120 allowed:414559436
    
    =WARNING REPORT==== 8-Aug-2014::00:12:01 ===
    memory resource limit alarm set on node &#39;rabbit@li370-61&#39;.
    
    **********************************************************
    *** Publishers will be blocked until this alarm clears ***
    **********************************************************
    
    =INFO REPORT==== 8-Aug-2014::00:12:07 ===
    Server startup complete; 0 plugins started.
    
    =ERROR REPORT==== 8-Aug-2014::00:15:32 ===
    ** Generic server rabbit_disk_monitor terminating 
    ** Last message in was update
    ** When Server state == {state,&quot;/var/lib/rabbitmq/mnesia/rabbit@li370-61&quot;,
                                   50000000,46946492416,100,10000,
                                   #Ref&lt;0.0.1.79456&gt;,false}
    ** Reason for termination == 
    ** {unparseable,[]}
    
    =INFO REPORT==== 8-Aug-2014::00:15:37 ===
    Disk free limit set to 50MB
    
    =ERROR REPORT==== 8-Aug-2014::00:16:03 ===
    ** Generic server rabbit_disk_monitor terminating 
    ** Last message in was update
    ** When Server state == {state,&quot;/var/lib/rabbitmq/mnesia/rabbit@li370-61&quot;,
                                   50000000,46946426880,100,10000,
                                   #Ref&lt;0.0.1.80930&gt;,false}
    ** Reason for termination == 
    ** {unparseable,[]}
    
    =INFO REPORT==== 8-Aug-2014::00:16:05 ===
    Disk free limit set to 50MB


**UPDATE:**
Seems like problem was solved when installed newest version of rabbitmq (3.3.4-1) from rabbitmq.com repository. Originally I had one installed (2.8.4) from Debian repositories. So far rabbitmq-server is working smoothly. I will update this post if issue comes back.

**UPDATE:**
Unfortunately after about 24 hours the issue reappeared where rabbitmq shut down and restarting the process would make it consume resources until it shuts down again within minutes.  

All Mnesia Solutions on Gang of Coders

Total of 1 Mnesia Solutions

RabbitMQ (beam.smp) and high CPU/memory load issue