[rabbitmq-discuss] Shovel stuck?

Emile Joubert emile at rabbitmq.com
Wed Aug 15 16:31:58 BST 2012

Hi Benjamin,

Thanks for this information. Would it be possible for you to run some
commands the next time you detect this condition? Your assistance and
the output from this will help alot to track down the problem.

rabbitmqctl eval 'supervisor2:which_children(rabbit_shovel_sup).'

In the output of this command you will see process identifiers formatted
like <x.y.z> where x, y and z are integers. For each process identifier
<x.y.z> can you also run

rabbitmqctl eval 'erlang:process_info(shell_default:pid(x,y,z)).'


On 15/08/12 15:06, Benjamin Ballard wrote:
> missing to have rabbit shovels to attempt to reconnect even if there
> is a failure during the starting phase of a rabbit shovel. Could i
> just detect the shovel failure and then create a new shovel when the
> first crashes out without restarting all of rabbit?

You may be able to restart shovel independently by issuing
rabbitmqctl eval 'application:stop(rabbitmq_shovel).'
rabbitmqctl eval 'application:start(rabbitmq_shovel).'


More information about the rabbitmq-discuss mailing list