[rabbitmq-discuss] Rabbit won't restart - no next heap size found

Matthias Radestock matthias at rabbitmq.com
Sat Sep 29 08:41:29 BST 2012


On 28/09/12 22:06, Mike Khristo wrote:
> Added a 200G swap... it used some of it, but still seg faults at
> startup.

Did it fail with the same error, i.e. "eheap_alloc: Cannot allocate ....
bytes of memory"? That would be kinda surprising.

Is there anything in the log files?

There are scenarios in which an error can trigger the writing of an 
enormous log message, and it's the latter that is exhausting memory. If 
so, the log should contain the error.

> Is there any way to split up the data on disk so I can get 2 rabbits
> up with half the data each?

Hmm. The following should work:

1) make a backup of the rabbit database dir

2) cd into the database dir and remove the "clean shutdown" markers with
    rm -f `find . -name "clean.dot"`
If rabbit was shut down cleanly there should be one of these per queue 
plus one each in the msg_store_persistent and msg_store_transient dirs. 
If rabbit wasn't shut down cleanly and those files aren't present then 
not to worry.

3) in the msg_store_persistent dir remove half the *.rdq files

4) start rabbit

Then process all the messages in that rabbit, stop it, restore the 
backup and repeat the above but this time removing the other half of the 
*.rdq files.



More information about the rabbitmq-discuss mailing list