[rabbitmq-discuss] Shovel stuck?

Alex Zepeda alex at inferiorhumanorgans.com
Wed Aug 15 18:57:47 BST 2012

On Wed, Aug 15, 2012 at 06:44:04PM +0100, Matthias Radestock wrote:

> The last entry's timestamp coincides with that in the shovel status. Is 
> there anything in the latter log *after* that point?

Here's the next few minutes of the log files:


It looks like I restarted rabbit around 7:13.  At that point it appeared as
if the shovel had been wedged for about 16 minutes (IIRC there were eight
messages in the 'heartbeat' queue, one is generated roughly every two minutes).

> What version of rabbitmq are you running?

2.8.5 from the debian packages on rabbitmq.com

Erlang should be whatever the latest Ubuntu 11.04 package is.

> Also, please post the output of
> rabbitmqctl eval 'supervisor2:which_children(rabbit_shovel_sup).'
> and
> rabbitmqctl eval '[io:format("~p:~n~s~n", [Pid, element(2, 
> erlang:process_info(Pid, backtrace))]) || {_, Pid, _, _} <- 
> supervisor2:which_children(rabbit_shovel_sup), Pid =/= undefined].'
> (all one line)

When I regain access to the sensor I will try this.  Right now I'm
just going through the log files I copied over the last time I was
able to log in (early yesterday).

- alex

More information about the rabbitmq-discuss mailing list