[rabbitmq-discuss] rabbitmq was shutdown unwanted

Tue May 22 10:50:52 BST 2012

Hi,

My current memory usage with top:

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND 

  1161 rabbitmq  20   0 6203m 5.4g 2360 S   25 34.4 213:07.12 beam.smp

The queues number:

# rabbitmqctl -p /somepath list_queues
Listing queues ...
queue_storm_actionlog   0
dev_queue_storm_actionlog       1607487

The status shows:

  {running_applications,[{rabbit,"RabbitMQ","2.7.0"},
                         {os_mon,"CPO  CXC 138 46","2.2.2"},
                         {sasl,"SASL  CXC 138 11","2.1.6"},
                         {mnesia,"MNESIA  CXC 138 12","4.4.10"},
                         {stdlib,"ERTS  CXC 138 10","1.16.2"},
                         {kernel,"ERTS  CXC 138 10","2.13.2"}]},
  {os,{unix,linux}},
  {erlang_version,"Erlang R13B01 (erts-5.7.2) [source] [64-bit] 
[smp:8:8] [rq:8] [async-threads:30] [kernel-poll:true]\n"},
  {memory,[{total,6124614216},
           {processes,4058585384},
           {processes_used,4058271696},
           {system,2066028832},
           {atom,1101009},
           {atom_used,1088876},
           {binary,1769349912},
           {code,11719137},
           {ets,281219504}]},
  {vm_memory_high_watermark,0.6},
  {vm_memory_limit,10114781184}]

Do you have any further suggestion? thanks.

> On 22/05/2012 03:00, Cloud DNS wrote:
>> Hi,
>>
>> My rabbitmq is running on Ubuntu 9.10 server 64bit.
>> The memory on this host is 16GB, CPU is two of Xeon E5410.
>> Last night rabbitmq got shutdown unwanted, the error log is:
>>
>> # cat startup_err
>> Erlang has closed
>>
>> Crash dump was written to: erl_crash.dump
>> eheap_alloc: Cannot allocate 4454408120 bytes of memory (of type "heap").
>> Aborted
>>
>>
>> After startup by hand, the current memory usage is:
>>
>> # free -m
>> total used free shared buffers cached
>> Mem: 16077 15712 364 0 13 11437
>> -/+ buffers/cache: 4262 11814
>> Swap: 3812 5 3806
>>
>>
>> So please help why it got down? how to avoid it later?
>> We have rabbitmq in important application. Thanks.
>>
>
> Well your rabbit has 'run out of memory' - or to be more precise, the OS
> is unable to provide allocation so the Erlang runtime has shut down.
>
> It's not clear from `free -m` what is really going on, but just checking
> after startup is probably insufficient to tell you anything. Perhaps
> running `ps` or `top` whilst rabbit is *busy* will tell you more. You
> can also use the management plugin or `rabbitmqctl status` on the
> command line to get more information about rabbit's memory usage.
>
> I would also suggest reading through http://www.rabbitmq.com/memory.html
> to help get an idea of what kind of tuning facilities are available.
>
> Cheers,
> Tim
>
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>