3 months ago
I have crash error but in logs i dont have error
Request ID:
vTUPsZCBSOSWkE5t0-QtfA
Pinned Solution
3 months ago
I found the root cause and resolved the issue.
The problem was related to Prisma connections — too many connections were being created, and after the container restart the application could not handle the load and crashed.
I fixed this by limiting/reusing Prisma connections and also added a global application wrapper that catches and reports crash errors.
As a result, the issue has been successfully resolved.
4 Replies
3 months ago
upstreamErrors:
"[{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":473,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":1026,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":501,"error":"connection closed unexpectedly"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":0,"error":"connection refused"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":5000,"error":"connection dial timeout"},{"deploymentInstanceID":"7270768a-40af-4bd6-8968-98e18039df28","duration":5000,"error":"connection dial timeout"}]"
GET
/api/products
502
15s
3 months ago
What port is your service listening on? And what port is your (custom) domain set to use?
3 months ago
are these the logs coming from your service or from another proxy in front of your service?
astrid
What port is your service listening on? And what port is your (custom) domain set to use?
3 months ago
I found the root cause and resolved the issue.
The problem was related to Prisma connections — too many connections were being created, and after the container restart the application could not handle the load and crashed.
I fixed this by limiting/reusing Prisma connections and also added a global application wrapper that catches and reports crash errors.
As a result, the issue has been successfully resolved.
Status changed to Solved brody • 3 months ago