Creating service p-mysql-82109>>>
REQUEST_HEADERS:
Accept : application/json
Authorization : [PRIVATE DATA HIDDEN]
Content-Length : 135
Content-Type : application/json
REQUEST_BODY: {"name":"p-mysql-82109","service_plan_guid":"b2138f35-44f9-44db-b712-c0c750495955","space_guid":"e300fceb-9f21-459e-bcc1-0a6e5068c642"}
. RESPONSE: [201]
RESPONSE_HEADERS:
connection : keep-alive
content-length : 836
content-type : application/json;charset=utf-8
date : Mon, 24 Feb 2014 18:59:28 GMT
location : /v2/service_instances/809e0a0a-3b96-478a-9894-abbf35a20543
server : nginx
x-content-type-options : nosniff
x-vcap-request-id : bb248278-a40c-428c-bf48-e26add7d6668
Without a request ID to work with, I would grep the cc logs for something unique about the request, maybe the name you gave to the service instance. You may find the vcap-request-id associated with the request from the client, even though cc isn't returning it to the client. Then you can grep the logs for it and see the whole conversation. See if CC can tell you more about why it is returning a 502.