<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thank you! It turns out my vhost name actually has "/" in the name. So I was specifying the wrong vhost name all along. I guess since the default vhost is "/", I was looking at it like uri, so I had to create vhost preceded by "/". <div><br></div><div>Always helpful to have another pair of eyes looking at the problem. </div><div><br></div><div><br></div><div>Two quick questions, is it possible to define multiple queue.bind in the same declaration? This is to shovel traffic from multiple exchanges. And can we use the <span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">Most-Recently-Declared-Queue in the resource definition and NOT have it persistent so if shovel dies, the queue dies with it instead of accumulate messages?</span></div><div><br></div><div><br></div><div>Thanks again,</div><div>Mark, happy shoveling.<br><div><br></div><div><br><div><div>On Apr 21, 2010, at 11:40 PM, Matthias Radestock wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Mark,<br><br>Mark Lin wrote:<br><blockquote type="cite">Wanted to get shovel to work, but am getting<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">{amqp_error,access_refused, "access to vhost 'vtest' refused for user<br></blockquote><blockquote type="cite">'shovel'", 'connection.open'}}<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">from the rabbit server.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I am sure the username and password are correct.<br></blockquote><br>Have you granted the 'shovel' user access to the vhost 'vtest'? See <br><a href="http://www.rabbitmq.com/admin-guide.html#set_permissions">http://www.rabbitmq.com/admin-guide.html#set_permissions</a> - so something like<br> rabbitmqctl set_permissions -p vtest shovel ".*" ".*" ".*"<br>should do the trick.<br><br><blockquote type="cite">From the bql security document,<br></blockquote><blockquote type="cite"><a href="http://www.rabbitmq.com/rabbitmq-bql.html#bql-security-rules">http://www.rabbitmq.com/rabbitmq-bql.html#bql-security-rules</a>, showing<br></blockquote><blockquote type="cite">the exact same error, it seems that I HAVE to use bql ...<br></blockquote><br>No, you don't have to use bql; rabbitmqctl (which ships with the broker) <br>is all you need.<br><br><blockquote type="cite">to grant permission to amq.default(which doesn't actually exist on<br></blockquote><blockquote type="cite">the OSX 1.7.0 build of rabbitmq).<br></blockquote><br>'amq.default' is a pseudonym for the otherwise nameless default <br>exchange. From <a href="http://www.rabbitmq.com/admin-guide.html#access-control">http://www.rabbitmq.com/admin-guide.html#access-control</a> ...<br><br>"For convenience RabbitMQ maps AMQP's default exchange's blank name to <br>'amq.default' when performing permission checks."<br><br>Whether or not the shovel user needs access to the default exchange <br>depends on the rest of your shovel configuration. But in any case the <br>".*" regexps in the above set_permissions call will cover that.<br><br><blockquote type="cite">By the way, the version of rabbitmq-shovel I downloaded via hg has a<br></blockquote><blockquote type="cite">few parameter modifications differ from given example in the blog.<br></blockquote><br>The shovel, like the rest of the code base, is evolving, so for the most <br>up to date documentation always refer to the docs shipped with the code, <br>i.e. <a href="http://hg.rabbitmq.com/rabbitmq-shovel/file/default/README">http://hg.rabbitmq.com/rabbitmq-shovel/file/default/README</a> in this <br>case.<br><br><br>Regards,<br><br>Matthias.<br></div></blockquote></div><br></div></div></body></html>