Got it going but it was just sheer luck... the 25th attempt to start it got it working, somehow. Even with 200G swap, it didn't help.<div><br><br><div class="gmail_quote">On Tue, Oct 9, 2012 at 11:30 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mike,<br>
<br>
did you make any progress on this?<br>
<br>
We have since discovered that rabbit can use lot of memory on recovery from an unclean shutdown, so this may well be the problem you are running into. We'll fix that in an upcoming release, but meanwhile the suggestions below should get you going.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.</font></span><div class="HOEnZb"><div class="h5"><br>
On 29/09/12 08:41, Matthias Radestock wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mike,<br>
<br>
On 28/09/12 22:06, Mike Khristo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Added a 200G swap... it used some of it, but still seg faults at<br>
startup.<br>
</blockquote>
<br>
Did it fail with the same error, i.e. "eheap_alloc: Cannot allocate ....<br>
bytes of memory"? That would be kinda surprising.<br>
<br>
Is there anything in the log files?<br>
<br>
There are scenarios in which an error can trigger the writing of an<br>
enormous log message, and it's the latter that is exhausting memory. If<br>
so, the log should contain the error.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there any way to split up the data on disk so I can get 2 rabbits<br>
up with half the data each?<br>
</blockquote>
<br>
Hmm. The following should work:<br>
<br>
1) make a backup of the rabbit database dir<br>
<br>
2) cd into the database dir and remove the "clean shutdown" markers with<br>
� � rm -f `find . -name "clean.dot"`<br>
If rabbit was shut down cleanly there should be one of these per queue<br>
plus one each in the msg_store_persistent and msg_store_transient dirs.<br>
If rabbit wasn't shut down cleanly and those files aren't present then<br>
not to worry.<br>
<br>
3) in the msg_store_persistent dir remove half the *.rdq files<br>
<br>
4) start rabbit<br>
<br>
Then process all the messages in that rabbit, stop it, restore the<br>
backup and repeat the above but this time removing the other half of the<br>
*.rdq files.<br>
<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>-mk<br>
</div>