[rabbitmq-discuss] RabbitMQ doesn't start after having crashed with "too many processes", "Last message in was {'$gen_cast', emit_stats}"

Marek Majkowski majek04 at gmail.com
Wed Aug 10 18:58:38 BST 2011

On Wed, Aug 10, 2011 at 16:59, Eugene Kirpichov <ekirpichov at gmail.com> wrote:
> I had a case where several thousand consumers from several hundred
> machines tried to connect to a single instance of rabbitmq (with 1
> connection per machine), causing it to die of "too many processes".
> The curious thing is that subsequently rabbitmq ***was not able to
> even start, until the process limit was increased.***
> Is this expected behavior?

In some cases - yes. For example if you have more durable queues
than available processes.

> I'm attaching the rabbitmq log, which contains both the brave death
> and futile startup attempts.

I can see the death indeed, I can't see restarts.


More information about the rabbitmq-discuss mailing list