Thanks so much!<br><br><div class="gmail_quote">On Tue, Apr 3, 2012 at 5:15 AM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Joseph,<br>
<div class="im"><br>
On 02/04/12 21:15, Joseph Marlin wrote:<br>
> I know I'm working on a version that's pretty old by now. I looked at<br>
> the log contents and was completely mystified. I'd like to understand<br>
> what went wrong here.<br>
><br>
> The Story: RabbitMQ crashes and when I bring it back up, all queue<br>
> contents from all my persistent queues are no longer there.<br>
><br>
> -If it was my fault, what can I do to fix it?<br>
> -If it is Rabbit's fault, has the issue been fixed?<br>
><br>
> Attached are the 'rabbitmqctl report' and the appropriate log from<br>
> /var/log/rabbitmq/<br>
<br>
</div>The log contains {error,enospc}. This means the disk ran out of space.<br>
The only way to prevent this condition is to monitor the disk free space<br>
and stop publishers or provision more space before space runs out.<br>
<br>
If you restart the broker while out of disk space then recovery of<br>
messages will fail. The broker makes a backup of the data directory<br>
first, but this would have failed.<br>
<br>
The next version of RabbitMQ (after v2.8.1) will deal with this<br>
condition more gracefully by throttling producers when disk space runs<br>
low as well as when RAM runs low.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
</font></span></blockquote></div><br>