[rabbitmq-discuss] Shovel 3.1.0 - terminates on unknown_host error instead of seeking another host

Tim Watson tim at rabbitmq.com
Fri May 10 13:39:00 BST 2013


On 10 May 2013, at 13:29, Laing, Michael P. wrote:

> Previously the shovel would always find one of the actual instances, or remain in the 'starting' state.
> Now the shovel terminates if a host is not found.
> We can smarten up our configuration but that doesn't address the real problem: if a host has failed, we want the shovel to always seek another host and not terminate.

Can you post your configuration (with scrubbed IP addresses if needed) please? This shouldn't happen, viz the shovel should attempt to reconnect. This could be a recurrence of http://rabbitmq.1065348.n5.nabble.com/Shovels-not-reconnecting-with-RabbitMQ-3-1-0-td26372.html, but I'd like to take a peek at your config and make sure. We've fixed that bug (see the nightly build) and the fix will out in 3.1.1 shortly (ish).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130510/67e0d983/attachment.htm>

More information about the rabbitmq-discuss mailing list