Help!!!!!!!!! Database timeout in recently
{ "clientVersion": "6.10.1", "code": "P1001", "meta": { "database_host": "qp-2045-production.c09wkquaajuf.us-east-1.rds.amazonaws.com", "database_port": 5432, "modelName": "PlatformInteractions" }, "name": "PrismaClientKnownRequestError", "stack": "PrismaClientKnownRequestError: \nInvalid
prisma.platformInteractions.update() invocation:\n\n\nCan't reach database server at qp-2045-production.c09wkquaajuf.us-east-1.rds.amazonaws.com:5432\n\nPlease make sure your database server is running at qp-2045-production.c09wkquaajuf.us-east-1.rds.amazonaws.com:5432.\n at Zn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7459)\n at Zn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6784)\n at Zn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6491)\n at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9778)"}6 Replies
Ahoy, knowledge seeker! I'm the Prisma AI Help Bot. Do you want a dev's response that might take a hot second, or an AI answer that's ready before your next coffee sip? Either way, your question is important to us.
Are you able to connect to the database with your AWS RDS Connection string via a Database IDE like pgAdmin, Tableplus etc?
Hi @Nurul yes able to connect through pgadmin
intermittent timeout errors still occurring.
for few times its works when added pgbounce=true in database URL
but now again start throwing errors
Please make sure your database server is running at
qp-2045-development.c09wkquaajuf.us-east-1.rds.amazonaws.com:5432.
{
"clientVersion": "6.10.1",
"code": "P1001",
"meta": {
"database_host": "qp-2045-development.c09wkquaajuf.us-east-1.rds.amazonaws.com",
"database_port": 5432,
"modelName": "PlatformInteractions"
},
"name": "PrismaClientKnownRequestError",
"stack": "PrismaClientKnownRequestError: \nInvalid db_prisma_1.db.platformInteractions.update() invocation in\n/app/dist/src/api-orchestration-module/api-orchestration.js:81:55\n\n 78 }\n 79 processActions(actions, platform) {\n 80 return __awaiter(this, void 0, void 0, function* () {\n→ 81 yield db_prisma_1.db.platformInteractions.update(\nCan't reach database server at qp-2045-development.c09wkquaajuf.us-east-1.rds.amazonaws.com:5432\n\nPlease make sure your database server is running at qp-2045-development.c09wkquaajuf.us-east-1.rds.amazonaws.com:5432.\n at Zn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7459)\n at Zn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6784)\n at Zn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6491)\n at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9778)"
}
URL:
postgresql://postgres:PASSWORD@AWS-RDS-HOST/DATABASE-NAME?connection_limit=50&pool_timeout=15&pgbouncer=trueDoes this error occur randomly?
Does it happen on the latest prisma version 6.11.1?
@Nurul thanks for reaching out
its start throwing this error on version "clientVersion": "6.10.1"
Its happened when multiple concurrent requests happed on cron and queue subscription
so combined requests at a time may 100-130 database requests
@Nurul
also i have one question:
if connection pool is not availble doesnt it wait those requests on queued and once connection is available it will execute those?
In any configurations for the same? please provide those!
i get the exact same error when i deployed my environment to kubernetes and going to an azure mysql server. It doesn't always happen and it looks like it is random.. I still haven't found the solution. my reasoning is that the network or my db shuts down the connection while the back-end application still think it is there. But I can't prove it yet nor that i can find a solution to mitigate this.