The erlang thing has bitten me in the past. On my laptop, RabbitMQ would get into a state where it was unavailable and taking 100% CPU. I think it happened whe

The erlang thing has bitten me in the past. On my laptop, RabbitMQ would get into a state where it was unavailable and taking 100% CPU. I think it happened when I switched networks (moved laptop home) and the spinning was from repeatedly crashing. I never sorted the root cause, just wrote a script to kill and restart rabbitMQ. (The script to kill rabbit was named 'fudd'.)