When I try to unbind my app from mariadb service I get:
Unexpected Response
Response code: 502
CC code: 0
CC error code:
Request ID: 48c77bfe-4c22-4e56-4d62-34fc113a10d4::166ca652-62ac-4829-8c37-5009c1796426
Description: {
"description": "Service instance gatewayDB: Service broker error: Internal Server Error",
"error_code": "CF-ServiceBrokerBadResponse",
"code": 10001,
"http": {
"uri": "http://open-service-broker.service.consul:8080/cf-broker/v2/service_instances/{service_instance}/service_bindings/{service-binding}",
"method": "DELETE",
"status": 500
}
}
I have all the rights for the organization/space.
EDIT:
When I try to restage the app with exiting mariadb service instance, I get Caused by: java.sql.SQLInvalidAuthorizationSpecException: Could not connect: Access denied for user '{username}'#'{host}' (using password: YES)
Maybe environment variables are causing this error?
We apologize for any inconvenience this issue caused to you. We fixed it and now the unbinding works fine.
This is an issue on the provider's side, please open a support ticket with them.
Related
I have been working on a project for a couple of months and when I tried to deploy updates today I was met with the following error: HTTP Error: 403, Write access to project was denied
This is not the first time I have called firebase deploy for this project but I haven't had any issues before.
The relevant section of the log generated with firebase deploy --debug:
[2023-02-14T09:05:36.343Z] >>> [apiv2][query] POST https://cloudfunctions.googleapis.com/v2/projects/galimbang-192cf/locations/us-central1/functions:generateUploadUrl [none]
[2023-02-14T09:05:37.947Z] <<< [apiv2][status] POST https://cloudfunctions.googleapis.com/v2/projects/galimbang-192cf/locations/us-central1/functions:generateUploadUrl 403
[2023-02-14T09:05:37.947Z] <<< [apiv2][body] POST https://cloudfunctions.googleapis.com/v2/projects/galimbang-192cf/locations/us-central1/functions:generateUploadUrl {"error":{"code":403,"message":"Write access to project 'galimbang-192cf' was denied","status":"PERMISSION_DENIED"}}
There was an issue deploying your functions. Verify that your project has a Google App Engine instance setup at https://console.cloud.google.com/appengine and try again. If this issue persists, please contact support.
⚠ functions: Upload Error: HTTP Error: 403, Write access to project 'galimbang-192cf' was denied
Error: HTTP Error: 403, Write access to project 'galimbang-192cf' was denied
[2023-02-14T09:05:37.950Z] Error Context: {
"body": {
"error": {
"code": 403,
"message": "Write access to project 'galimbang-192cf' was denied",
"status": "PERMISSION_DENIED"
}
},
"response": {
"statusCode": 403
}
}
I should also note that this project uses the Next.JS firebase integration.
I try to deploy AWS MWAA via Cloudformation but come accross:
Resource handler returned message: "Invalid request provided: Internal server error (Service: Mwaa, Status Code: 500, Request ID: 21fea850-9cf7-4977-a947-d10dd3cc1a13)" (RequestToken: f2384bd0-68a6-44d3-d57d-fed3a52f817b, HandlerErrorCode: InvalidRequest)"
on the MWAA resource itself. The other ressources (LoadBalancer, Listener, etc...) are correctly deployed.
What are my solutions to debug this? Since the error message is not explicit and the resource is not created (so it has no logs).
I am trying to do follow the ibm tutorial for object detection (https://cloud-annotations.github.io/training/object-detection/wml/) and i have a problem when I try to connect to the machine. Here are the credentials
{
"apikey": "kIlCEVrah4Yi2Jexs4f6ryxtXK_UmlRRYbEHFDZPj3-U",
"iam_apikey_description": "Auto generated apikey during resource-key operation for
Instance - crn:v1:bluemix:public:pm-20:eu-
gb:a/ba2f381a117d49a8898e3b9d244488cc:07c9e765-ab56-4303-a02d-ff487a394db0::",
"iam_apikey_name": "auto-generated-apikey-0cb1a7b2-7037-45d8-9221-73116bf42f7b",
"iam_role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
"iam_serviceid_crn": "crn:v1:bluemix:public:iam-
identity::a/ba2f381a117d49a8898e3b9d244488cc::serviceid:ServiceId-
6f725bc1-f6d1-4a62-a7da-d8701494ad1e",
"instance_id": "07c9e765-ab56-4303-a02d-ff487a394dba",
"password": "0fda17b6-5b97-4cf3-ba69-ed355555b45a",
"url": "https://eu-gb.ml.cloud.ibm.com",
"username": "0cb1a7b2-7037-45d8-9221-73116bf42f7a"
}
and when i paste the username / password and instance_id i get the next error:
Status code: 404, body: {"trace":2894125269067430410,"errors":
[{"code":"not_found","message":"User with given credentials not found.","target":
{"type":"field","name":"token"},"moreInfo":null}]}
Any help would be awesome! Thank you!
If you are following the instructions in the link you provided, then you are have most likely taken the wrong instance_id or not specified the url in the connection.
Your service credentials are showing https://eu-gb.ml.cloud.ibm.com which will be running on the UK hosted servers, which I am guessing will not be the default.
We are getting below error while using Bluemix API Connect service. The same service was working fine few days back.
Error Message:
root request.py invoke_request: Response is: { "httpCode":"500", "httpMessage":"Internal Server Error", "moreInformation":"Failed to establish a backside connection" }
Thanks in advance.
Any resolution/mitigation on this?
The issue can be reproduced on API explorer (https://graphexplorer2.azurewebsites.net) with following REST API Repro steps:
Logon API Explorer with your tenant, https://graphexplorer2.azurewebsites.net
Get the group conversation attachments with following API In my case:
You will get following error:
Request duration: 6086 ms. CollapseExpandRawJSON Error: 500 - Internal Server Error See Response Headers for details. { "error": { "code": "ErrorInternalServerError", "message": "Unable to cast object of type 'Microsoft.Exchange.Services.OData.Model.AttachmentSchema' to type 'Microsoft.Exchange.Services.OData.Web.IRequestBuilderForEntitySet`2[Microsoft.Exchange.Services.OData.Model.Post,Microsoft.Exchange.Services.OData.Model.Attachment]'.", "innerError": { "request-id": "89efeca6-ba17-478b-aa8e-f3bf6ec32cd0", "date": "2016-01-08T09:56:39" } } }
Thanks,
Raymond
This was a bug in the service. The fix for it is being rolled out and you should no longer see the error.