Jellyton
Jellyton
Explore posts from servers
PPrisma
Created by Jellyton on 4/30/2024 in #help-and-questions
Health Check of Query Engine timed out.
Hello there, I've been using Prisma for a bit now and I decided today to setup Prisma Accelerate. I'm using a mariadb (mysql) server and I've successfully setup accelerate, however, when queries that worked before accelerate are run, they error. Error + Logging:
prisma:client clientVersion 5.13.0 +0ms
prisma:warn In production, we recommend using `prisma generate --no-engine` (See: `prisma generate --help`)
prisma:client Prisma Client call: +459ms
prisma:client prisma.mdt_incidents.findUnique({
where: {
id: 13211
}
}) +1ms
prisma:client Generated request: +0ms
prisma:client {
"modelName": "mdt_incidents",
"action": "findUnique",
"query": {
"arguments": {
"where": {
"id": 13211
}
},
"selection": {
"$composites": true,
"$scalars": true
}
}
}
+1ms
⨯ PrismaClientKnownRequestError:
Invalid `prisma.mdt_incidents.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: Health Check of Query Engine timed out."}} (The request id was: 87c55c720a5eeb77)
prisma:client clientVersion 5.13.0 +0ms
prisma:warn In production, we recommend using `prisma generate --no-engine` (See: `prisma generate --help`)
prisma:client Prisma Client call: +459ms
prisma:client prisma.mdt_incidents.findUnique({
where: {
id: 13211
}
}) +1ms
prisma:client Generated request: +0ms
prisma:client {
"modelName": "mdt_incidents",
"action": "findUnique",
"query": {
"arguments": {
"where": {
"id": 13211
}
},
"selection": {
"$composites": true,
"$scalars": true
}
}
}
+1ms
⨯ PrismaClientKnownRequestError:
Invalid `prisma.mdt_incidents.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: Health Check of Query Engine timed out."}} (The request id was: 87c55c720a5eeb77)
3 replies