[rabbitmq-discuss] Proper protocol for dealing with crash dumps?

Alex Zepeda alex at inferiorhumanorgans.com
Mon Oct 8 20:20:06 BST 2012

On Sun, Oct 07, 2012 at 08:05:22AM +0100, Matthias Radestock wrote:

> The total memory and high watermark are shown in the rabbit logs, e.g.
> s.t. like
> =INFO REPORT==== 3-Oct-2012::20:31:08 ===
> Memory limit set to 4814MB of 12036MB total.
> So check that these figures make sense for your setup.

=INFO REPORT==== 8-Oct-2012::10:00:43 ===
Memory limit set to 395MB of 988MB total.

> As suggested previously, when rabbit is using more memory than you
> expect the output of 'rabbitmqctl report' should shed some light on
> where it's going.

I'll try, but generally the devices having the most trouble have the
most unreliable connections, so logging in is often very difficult.

The other thing I'm seeing is that shovel appears to be getting
stuck (but the shovel status shows it's running) on a number
of these devices.  What sort of diagnostics would be useful

- alex

More information about the rabbitmq-discuss mailing list