<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On 10 May 2013, at 13:29, Laing, Michael P. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div><div>Previously the shovel would always find one of the actual instances, or remain in the 'starting' state.</div><div><br></div><div>Now the shovel terminates if a host is not found.</div><div><br></div><div>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.</div><div><br></div></div></div></blockquote><br></div><div>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 <a href="http://rabbitmq.1065348.n5.nabble.com/Shovels-not-reconnecting-with-RabbitMQ-3-1-0-td26372.html">http://rabbitmq.1065348.n5.nabble.com/Shovels-not-reconnecting-with-RabbitMQ-3-1-0-td26372.html</a>, 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).</div><div><br></div><div>Cheers,</div><div>Tim</div><br></div></body></html>