MentorVentor
MentorVentor
PPrisma
Created by MentorVentor on 8/19/2024 in #help-and-questions
Checklist for migration of underlying database from AWS RDS to Azure
Hi, We are going to shift our database from AWS RDS to Azure. We are currently using Prisma Accelerate and Prisma ORM both which are being used from AWS lambda functions. Now we are going to migrate the entire underlying databse to Azure from AWS today. Do we need to follow any extra steps etc or be mindful of any things w.r.t. Prisma? Assuming that the DB is replicated accurately are there any chances of things going wrong for prisma? Do we need to run some commands etc on the new DB before changing the connection string in Prisma Accelerate? Will everything work out of the box? Couldn't find documentation on this through Googling, hence asking here. P.S. I've raised a support ticket officially as well but posting here just in case someone from the community has done it before
3 replies
PPrisma
Created by MentorVentor on 8/13/2024 in #help-and-questions
Getting `Can't reach database server ` long after DB load has dialed down
Hi, We are using prisma accelerate. Somehow we are getting this error, DESPITE our db being completely accessible through other tools (like psql and dbeaver etc). There was a heavy load at 13:30 GMT but it has been more than 1 hour since that and we still continue to get this error. Can anyone help us with 1. What to do to immediate fix this? Could this be a cache issue on prisma accelerate side? 2. What's the root cause and how do we fix that and prevent this from happening again?
"message": "\nInvalid `prisma.organizations.findFirst()` invocation:\n\n\nCan't reach database server at `db.peakmind.in:5432`\n\nPlease make sure your database server is running at `<OUR SERVER URL`."
"message": "\nInvalid `prisma.organizations.findFirst()` invocation:\n\n\nCan't reach database server at `db.peakmind.in:5432`\n\nPlease make sure your database server is running at `<OUR SERVER URL`."
9 replies
PPrisma
Created by MentorVentor on 6/23/2024 in #help-and-questions
Getting P2024 all of a sudden without any unusual activity or usage spike
Hi, We've suddenly started receiving the error P2024 in our prisma setup (we also have prisma accelerate) seemingly out of the blue. I've checked that there is no sudden load (in-fact load is slightly less than usual right now) Couldn't find much info on how to debug and fix this in the docs, can someone help? Here's the error message btw
{
"message": "\nInvalid `prisma.user_identification_types.findFirst()` invocation:\n\n\nTimed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 10)"
}
{
"message": "\nInvalid `prisma.user_identification_types.findFirst()` invocation:\n\n\nTimed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 10)"
}
3 replies
PPrisma
Created by MentorVentor on 4/19/2024 in #help-and-questions
Need urgent support from Prisma team
Hi, Our production app on accelerate is breaking with an unknown error from Prisma, can someone from Prisma help asap? This is super critical for a new client launch today. Our DB is completely fine. We are unable to interpret the error as well { "message": "\nInvalid prisma.resource_tags.findMany() invocation:\n\n\nUnknown server error: {"type":"UnknownTextError","body":"Internal Server Error"} (The request id was: 876d9de9fb090e1c)" }
3 replies