You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an exchange is declared a check is performed to see if the exchange exists. This check posts an error since the specified credentials are not being passed to the call. This is the same symptom that was fixed for the actual creation of the exchange in release 3.1.0. The exchange is created but there is still an error message logged since the default credentials do not have access to list the exchanges.
The rabbitmqadmin command is:
/usr/local/bin/rabbitmqadmin list exchanges
It should be:
/usr/local/bin/rabbitmqadmin list exchanges --user= --password=
The text was updated successfully, but these errors were encountered:
@RColeman This doesn't seem to have shown up in the new ticketing system. I've cleaned up issue #149 , but this is still present. If you do have the default users prefetch fails to find the exchanges for another vhost, and always recreates them.
If you do not have the defaults enabled, you end up w/ errors. This functionality is called from the puppetlabs/mcollective forge module, btw...
When an exchange is declared a check is performed to see if the exchange exists. This check posts an error since the specified credentials are not being passed to the call. This is the same symptom that was fixed for the actual creation of the exchange in release 3.1.0. The exchange is created but there is still an error message logged since the default credentials do not have access to list the exchanges.
The rabbitmqadmin command is:
/usr/local/bin/rabbitmqadmin list exchanges
It should be:
/usr/local/bin/rabbitmqadmin list exchanges --user= --password=
The text was updated successfully, but these errors were encountered: