[rabbitmq-discuss] Rabbit-MQ crashing
sconover at gmail.com
Sun Jan 3 17:05:55 GMT 2010
We're experiencing this problem as well. Just from reading the list
it seems that the new persister stuff committed around 12/1 is
supposed to fix it.
- has this bug indeed been fixed?
- is the code somewhere past bleeding edge? Would you consider it to be stable?
- please excuse my ignorance, but is there any bug or ticket url that
I can follow to keep track of the fix / when it's been released / etc
On Thu, Nov 12, 2009 at 6:25 AM, Tony Garnock-Jones <tonyg at lshift.net> wrote:
> Hi Derek,
> (Replying here as well for the archive)
> Derek Burdick wrote:
>> I have a durable, fanout exchange and queue. I post persistent messages
>> to the exchange. After sending messages for some time, the ERL process
>> stops and I can not restart RabbitMQ without deleting the contents of
>> the Database. Here is the log from startup:
> RabbitMQ has become overfull, and crashed during persister log rollover
> as a result. You probably have a zero-byte-long rabbit_persister.LOG,
> and a large rabbit_persister.LOG.previous. Make a backup of the
> .previous file somewhere else, just in case, and then copy it over top
> of the rabbit_persister.LOG file and start the broker. You shouldn't
> need to delete the whole database.
> We're working on fixing the underlying cause, but for now, you must not
> store more messages than (some proportion of) your available RAM can
> hold. If you are simply buffering things without trying to consume them,
> then you will probably need to introduce some consumers of some kind :-)
> and if you do have consumers running, but Rabbit is running out of
> memory anyway, you should probably check that you are acknowledging
> deliveries from the broker properly.
>  Tony Garnock-Jones | Mob: +44 (0)7905 974 211
>  LShift Ltd | Tel: +44 (0)20 7729 7060
>   http://www.lshift.net/ | Email: tonyg at lshift.net
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss