Suddenly got P6008 out of nowhere
I've never had this issue before but now suddently lots of my requests to prisma are failing:
PrismaClientKnownRequestError:
Invalid
prisma.user.findUnique() invocation:
This request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: Too many failed attempts to connect to database. Try again after 2025-01-29T09:34:37.615Z"}} (The request id was: 909839ca5e0971f3)
at zr.handleRequestError (/var/task/node_modules/@prisma/client/runtime/edge.js:20:7987)
at zr.handleAndLogRequestError (/var/task/node_modules/@prisma/client/runtime/edge.js:20:7295)
at zr.request (/var/task/node_modules/@prisma/client/runtime/edge.js:20:6985)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async l (/var/task/node_modules/@prisma/client/runtime/edge.js:29:9558)
at async I (/var/task/.next/server/app/api/flashcards/cards-from-upload-notes/route.js:1:3555)
at async /var/task/.next/server/chunks/6937.js:14:49829
at async /var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:37010
at async eC.execute (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27552)
at async eC.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38344) {
code: 'P5000',
clientVersion: '5.21.1',
meta: { modelName: 'User' }
}8 Replies
You chose to debug with a human. They'll tinker with your query soon. If you get curious meanwhile, hop into
#ask-ai for a quick spin!Hey 👋
Can you share the email id or GitHub handle with which you signed up? I would like to take a look at logs for your environment
Yeah my email is [email protected]
SS Azure - Production is the workspace
Thanks 🙂
I checked the logs and I see the same error: "Accelerate was not able to connect to your database. The underlying error is: Too many failed attempts to connect to database. Try again after 2025-01-29T09:34:37.615Z"
Do you see any issues during that time on your database end?
It also looks like a new Query Engine was allocated to your environment during the same time.
Do you still see the same error?
Yeah i've been getting it on/off the last day or two
These are the order of the prisma requests if that helps:
Do you see any errors in your database logs during that time?