[rabbitmq-discuss] Persister logs never getting rolled/cleaned up?

[Steve Garrity]

Apologies if this is a n00b question, which I think it is, but we're
running a plain vanilla install of rabbitmq 2.1.1 on erlang r14B with
celeryd 2.1.4 and we're continually running into persister log issues
and Google has thus far not turned up results.

Every few weeks rabbit just stops accepting new connections...stopping
and starting rabbit takes on the order of 15 minutes and it just
continues to choke once it gets started again. Looking at /var/lib/
rabbitmq/mnesia/rabbit shows ~170MB of persister logs (this is running
on a 1GB RAM machine, so the vm memory alarm is set at ~400MB (which
we routinely bounce off of trying to reload these logs). By deleting
(or renaming) this directory, recreating users/vhosts, and restarting
rabbit, everything works great again (for a few weeks).

This led us to believe we were using celery incorrectly and
accidentally persisting results for all time, but we've tried with
ignore_result=True, delivery_mode=transient, durable=False, and
result_persistent=False and nothing seems to fix it.

These don't seem like logs that we should have to rotate
manually...can someone point us in the right direction?

Thanks! /s