Re: Resource Conflict error in RabbitMQ broker.

Guruprakash S <prakash.guru4@...>

When trying to register a service against the RabbitMQ broker using cf


*cloudfoundry(a)micro-deploy-uspl:~/persis-store/deploy/initial$ cf
create-service p-rabbitmq standard ngis-rabbit-platformngis(a)

*Creating service ngis-rabbit-platformngis(a)
<ngis-rabbit-platformngis(a)> in org EMC / space ngisspace as admin...*


*Server error, status code: 409, error code: 10001, message: Resource

We narrowed down the problem by circumventing the Cloud Controller and
trying to register against the RabbitMQ Broker directly.

The broker seems to be the culprit – we tried registering the service
against it directly using the following on the broker VM itself:

*curl http://administrator:password(a)
-d '{"organization_guid":
"7e27e716-24da-44cb-8f60-65506efb7df2"}' -X PUT -H
"X-Broker-API-Version: 2.6" -H "Content-Type: application/json**”*

It still resulted in throwing errors about the service already existing:

*2016-May-07 22:15:30 +0000 localhost INFO
[io.pivotal.pcf.rabbitmq.server] - Asked to provision a service:

*2016-May-07 22:15:30 +0000 localhost WARN
[io.pivotal.pcf.rabbitmq.server] - Vhost rabbitmq-test already exists*

*2016-May-07 22:15:30 +0000 localhost INFO
[io.pivotal.pcf.rabbitmq.server] - PUT
/v2/service_instances/rabbitmq-test 409 2 (in 32 ms)*

Essentially we need to understand why we can’t register any services
against the RabbitMQ broker.

On Sun, May 8, 2016 at 7:20 AM, William Martin <wmartin(a)> wrote:

You can find the relevant code for this at:

Is it possible you have an orphaned service instance (a vhost on your
rabbit cluster). I'd be surprised to see this error from a `cf
create-service`, how are you trying to provision?

On Sat, May 7, 2016 at 10:44 PM, Guruprakash S <prakash.guru4(a)>


We are seeing this error while creating a service instance against a
latest RabbitMQ deployment which we just deployed:

Server error, status code: 409, error code: 10001, message: Resource

We checked the CC database table service_instances to see if there are
any service_instances related to RMQ and we don't see any there.

Request your help.


Join { to automatically receive all group messages.