Prisma•5mo ago

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`."

5 Replies

Nurul•5mo ago

Hey @MentorVentor Are you getting this error on all your queries or only on specific queries? What is your GitHub Handle?

MentorVentorOP•5mo ago

Only on one specific query, although that is the query that gets disproportionately higher invocations dev-peakmind is my github handle

Nurul•5mo ago

Thanks for sharing your handle, let me take a look Does this happen in "Peakmind Production" project?

MentorVentorOP•5mo ago

Yes

Nurul•5mo ago

Is this still happening? I was in touch with Peakmind team in context of the db migration. Does it still happen in your new database?

Gaming

Programming

Getting `Can't reach database server ` long after DB load has dialed down