[rabbitmq-discuss] "Other process memory" growth

Emile Joubert emile at rabbitmq.com
Thu Mar 28 14:48:04 GMT 2013

Hi Carl,

On 28/03/13 09:06, carlhoerberg wrote:
> Ok :) https://www.dropbox.com/sc/mb7zw9gqsrxg7to/H0x1QYwfau

Would you be able to provide some more details for us to investigate
this further? We will need to logfiles and the sasl logfiles from all 3
nodes. Please provide entries from at least a while before the memory
use on the one node started to increase.

Then we'd like you to execute a command on the node with abnormal memory
(tiger01), but take some precautions first. If you are able to bring
more swapspace online then please do so. If there are any other
non-critical processes on the machine then please stop them, as this
command has the potential to impose heavy load. Please be aware that
this command could cause the node to crash. If you have HA redundancy in
place then it shouldn't matter, but if you are not comfortable with this
prospect then don't proceed.

Otherwise please run this command:

rabbitmqctl eval 'io:put_chars(standard_error, "this should appear in

and check that the expected text appeared in startup_err (normally in
/var/log/rabbitmq). If the text did not appear then do not proceed.

Otherwise please run this command:

rabbitmqctl eval 'erlang:process_display(element(2,
hd(lists:reverse(lists:sort([{process_info(P, memory), P} ||  P <-
erlang:processes()])))), backtrace).'

The command will return and the startup_err file should start growing
soon afterwards. It could take a long time until it stops growing. When
it does stop growing please send it to support at rabbitmq.com along with
the logfiles, preferably compressed.


More information about the rabbitmq-discuss mailing list