[regression] `Schema engine error` in Prisma 5.19.0 #25101

satadhi · 2024-08-28T10:33:02Z

Bug description

Version 5.19.0 appears broken to me. npx prisma migrate dev --name init simply gives error

risma:getConfig Using getConfig Wasm +0ms
prisma:getConfig config data retrieved without errors in getConfig Wasm +1ms
Error: Error: Schema engine error:

    at Cf (/home/satadhi.halde/Documents/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:432:1600)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async nl (/home/satadhi.halderDocuments/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:513:1789)
    at async Sm.parse (/home/satadhi.halderDocuments/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:943:72)
    at async s2t (/home/satadhi.halderDocuments/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:2002:1678)

How to reproduce

Followed steps in nestjs docs

The env file looks like this.

DATABASE_URL="mysql://root:password@127.0.0.1:3306/nestjs_prisma"

MYSQL_DATABASE=nestjs_prisma
MYSQL_ROOT_PASSWORD=password

I use docker-compose.yaml to run sql

services:
  mysql:
    image: mysql
    env_file:
      - .env
    ports:
      - '3306:3306'

Expected behavior

It should just run normally. I tried using version 5.18.0 everything works expected

Prisma information

// Add your schema.prisma
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

model Product {
  id   Int    @id @default(autoincrement())
  name String
}

Environment & setup

OS: Ubuntu 22.04.2 LTS
Database: MySQL
Node.js version: 20.14.0

Prisma Version

5.19.0

The text was updated successfully, but these errors were encountered:

callumJPritchard · 2024-08-28T11:05:05Z

I'm also trying to deal with a bug moving up to 5.19
On the face of it only somewhat related since I'm doing prisma db push --force-reset and then a seed script for our dev pipeline, however it's the same situation where things work until moving to 5.19.0

the db push seems to work, as does the initial part of the seed script until it gets to a particular function then it throws:

return prisma4.modelName.findUniqueOrThrow(
The column `t15.fieldName` does not exist in the current database

the code causing this is:

prisma.modelName.findUniqueOrThrow({
        where: { id },
        include: {
            relatedModel: {
                where: {
                    type: {
                        fieldName: false
                    }
	...

it almost looks like 5.19.0 is getting confused around the nested where clause an expecting fieldName on modelName instead?

to reiterate: the code is identical to what has been running for weeks. Only prisma version change causes the error

satadhi · 2024-08-28T11:08:10Z

Yes, I was trying to run hello world of prisma as I am learning prisma now.
Spent a full day on this lol. This is very sad

jkomyno · 2024-08-28T13:23:53Z

it almost looks like 5.19.0 is getting confused around the nested where clause an expecting fieldName on modelName instead?

Hi @callumJPritchard, please open a new issue for that. You're describing a possible bug in Prisma Client, not on prisma migrate. Thanks!

jkomyno · 2024-08-28T13:33:58Z

Hey @satadhi, can you please run the following command, and report back the output? Thanks.

npx prisma --version

This gives us much more information than just "5.19.0", and may help us assessing this further. Thanks!

satadhi · 2024-08-28T13:35:05Z

@jkomyno
Hi its all linked sir, my npm install @prisma/client is also broken which is of version 5.19.0.
Manually changing the version to 5.18.0 works fine.

I have used the basic setup of nestjs.

Below is the error when i used 5.19.0

PrismaClientInitializationError: Unable to require(/home/satadhi/Documents/nestjs-practise/prisma-prac/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node).
The Prisma engines do not seem to be compatible with your system. Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: /lib/x86_64-linux-gnu/libssl.so.1.1: version OPENSSL_1_1_1' not found (required by /home/satadhi/Documents/nestjs-practise/prisma-prac/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node)

aqrln · 2024-08-28T13:44:45Z

@satadhi this is unexpected but is there a reason you have OpenSSL 1.1 installed on your system? Did you install it with apt or in some other way? Right now Prisma prefers an older version of OpenSSL when multiple are installed for reasons, so if you only left OpenSSL 3 installed (which should be the default on Ubuntu 22.04) and regenerated the client, it should resolve the issue.

We should investigate what looks like a sudden bump in the requirements from OpenSSL 1.1.0 to OpenSSL 1.1.1 regardless. Maybe it comes from prisma/prisma-engines#4965.

satadhi · 2024-08-28T13:46:57Z

Hi @jkomyno

satadhi.halder: ~/Documents/nestjs - practise / prisma - prac$ npx prisma--version
Environment variables loaded from.env
Error: Unable to require(`/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
The Prisma engines do not seem to be compatible with your system.Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: /lib/x86_64 - linux - gnu / libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
    at pne (/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:284:116)
    at lWe (/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/prisma/build/index.js:284:269)
Error: Command failed with exit code 1: /home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version
/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
    at eke(/home/satadhi.halder / Documents / nestjs - practise / prisma - prac / node_modules / prisma / build / index.js: 5: 57)
at / home / satadhi.halder/Documents/nestjs - practise / prisma - prac / node_modules / prisma / build / index.js: 5: 10625
    at process.processTicksAndRejections(node: internal / process / task_queues: 95: 5)
    at async lWe(/home/satadhi.halder / Documents / nestjs - practise / prisma - prac / node_modules / prisma / build / index.js: 284: 343) {
  shortMessage: 'Command failed with exit code 1: /home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
    command: '/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
      escapedCommand: '"/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x" --version',
        exitCode: 1,
          signal: undefined,
            signalDescription: undefined,
              stdout: '',
                stderr: "/home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /home/satadhi.halder/Documents/nestjs-practise/prisma-prac/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)",
                  failed: true,
                    timedOut: false,
                      isCanceled: false,
                        killed: false
}
prisma: 5.19.0
@prisma/client          : 5.19.0
Computed binaryTarget: debian - openssl - 1.1.x
Operating System: linux
Architecture: x64
Node.js                 : v20.14.0
Query Engine(Node - API) : E_CANNOT_RESOLVE_VERSION(at node_modules / @prisma / engines / libquery_engine - debian - openssl - 1.1.x.so.node)
Schema Engine: E_CANNOT_RESOLVE_VERSION(at node_modules / @prisma / engines / schema - engine - debian - openssl - 1.1.x)
Schema Wasm: @prisma/prisma-schema-wasm 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b902f
Default Engines Hash: 5fe21811a6ba0b952a3bc71400666511fe3b902f
Studio: 0.502.0
satadhi.halder: ~/Documents/nestjs - practise / prisma - prac$

satadhi · 2024-08-28T13:49:30Z

@satadhi this is unexpected but is there a reason you have OpenSSL 1.1 installed on your system? Did you install it with apt or in some other way? Right now Prisma prefers an older version of OpenSSL when multiple are installed for reasons, so if you only left OpenSSL 3 installed (which should be the default on Ubuntu 22.04) and regenerated the client, it should resolve the issue.

We should investigate what looks like a sudden bump in the requirements from OpenSSL 1.1.0 to OpenSSL 1.1.1 regardless. Maybe it comes from prisma/prisma-engines#4965.

@aqrln yes when i got error i tried to manually install OpenSSL using command sudo apt-get install libssl1.1 . But it was of no use; after that i changed the version to 5.18.0 of @prisma/client . And it worked fine

aqrln · 2024-08-28T13:56:23Z

@satadhi so the OpenSSL error is a separate issue and unrelated to the original problem you were facing, right? It's better to uninstall it, yes, there's no reason to use OpenSSL 1.1 which has been officially EOL upstream for a year already (even if distros may still support it).

aqrln · 2024-08-28T13:59:08Z

Could you please also post your npx prisma --version output after removing OpenSSL 1.1?

satadhi · 2024-08-28T14:06:14Z

removed,

satadhi.halder:~/Documents/nestjs-practise/prisma-prac$ dpkg -l | grep libssl
ii  libssl3:amd64                              3.0.2-0ubuntu1.17                       amd64        Secure Sockets Layer toolkit - shared libraries

Output of npx prisma --version

$ npx prisma --version
Environment variables loaded from .env
prisma                  : 5.19.0
@prisma/client          : 5.19.0
Computed binaryTarget   : debian-openssl-3.0.x
Operating System        : linux
Architecture            : x64
Node.js                 : v20.14.0
Query Engine (Node-API) : libquery-engine 5fe21811a6ba0b952a3bc71400666511fe3b902f (at node_modules/@prisma/engines/libquery_engine-debian-openssl-3.0.x.so.node)
Schema Engine           : schema-engine-cli 5fe21811a6ba0b952a3bc71400666511fe3b902f (at node_modules/@prisma/engines/schema-engine-debian-openssl-3.0.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b902f
Default Engines Hash    : 5fe21811a6ba0b952a3bc71400666511fe3b902f
Studio                  : 0.502.0

mathiasayivor · 2024-08-31T00:52:17Z

I'm also getting the same error just after upgrading prisma from 5.18.0 to 5.19.0

After I run yarn prisma db push, I get the following error:

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "genesis", schema "public" at "127.0.0.1:5432"

Error: Schema engine error:

Running yarn prisma --version gives me the following:

Environment variables loaded from .env
Error: Unable to require(`/my-app/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
The Prisma engines do not seem to be compatible with your system. Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
    at pne (/my-app/node_modules/prisma/build/index.js:284:116)
    at lWe (/my-app/node_modules/prisma/build/index.js:284:269)
Error: Command failed with exit code 1: /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version
/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
    at eke (/my-app/node_modules/prisma/build/index.js:5:57)
    at /my-app/node_modules/prisma/build/index.js:5:10625
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async lWe (/my-app/node_modules/prisma/build/index.js:284:343) {
  shortMessage: 'Command failed with exit code 1: /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
  command: '/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
  escapedCommand: '"/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x" --version',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: "/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)",
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
prisma                  : 5.19.0
@prisma/client          : 5.19.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.18.2
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at ../node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : E_CANNOT_RESOLVE_VERSION (at ../node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b902f
Default Engines Hash    : 5fe21811a6ba0b952a3bc71400666511fe3b902f
Studio                  : 0.502.0
Preview Features        : omitApi

jkomyno · 2024-08-31T14:33:04Z

@satadhi this is unexpected but is there a reason you have OpenSSL 1.1 installed on your system? Did you install it with apt or in some other way? Right now Prisma prefers an older version of OpenSSL when multiple are installed for reasons, so if you only left OpenSSL 3 installed (which should be the default on Ubuntu 22.04) and regenerated the client, it should resolve the issue.

We should investigate what looks like a sudden bump in the requirements from OpenSSL 1.1.0 to OpenSSL 1.1.1 regardless. Maybe it comes from prisma/prisma-engines#4965.

prisma/prisma-engines#4965 was released in the dev Prisma version 5.19.0-dev.8.

@satadhi and @mathiasayivor, could you please try installing prisma@5.19.0-dev.7 and run prisma --version, and then repeat the process with prisma@5.19.0-dev.8?

Also, can you run the command above with DEBUG="prisma:get-platform" prisma --version, and post the output here? Thanks.

mathiasayivor · 2024-08-31T15:02:22Z

@jkomyno I've installed both prisma@5.19.0.-dev.7 and prisma@5.19.0-dev.8 outputs are below:

CMD: yarn prisma db push

prisma@5.19.0-dev.7:

Works as expected

prisma@5.19.0-dev.8:

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "genesis", schema "public" at "127.0.0.1:5432"

Error: Schema engine error:

CMD: DEBUG="prisma:get-platform" prisma --version

prisma@5.19.0-dev.7:

prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +1252ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +10ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +22ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
Environment variables loaded from .env
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +2303ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +1ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +12ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
prisma                  : 5.19.0-dev.7
@prisma/client          : 5.18.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.18.2
Query Engine (Node-API) : libquery-engine 44f753d2ce0008a24ce36e34aff65a5afe266839 (at ../node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : schema-engine-cli 44f753d2ce0008a24ce36e34aff65a5afe266839 (at ../node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.19.0-8.44f753d2ce0008a24ce36e34aff65a5afe266839
Default Engines Hash    : 44f753d2ce0008a24ce36e34aff65a5afe266839
Studio                  : 0.502.0
Preview Features        : omitApi

prisma@5.19.0-dev.8:

prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +1238ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +5ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +12ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
Environment variables loaded from .env
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +2199ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +2ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +12ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
Error: Unable to require(`/my-app/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
The Prisma engines do not seem to be compatible with your system. Please refer to the documentation about Prisma's system requirements: https://pris.ly/d/system-requirements

Details: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
    at one (/my-app/node_modules/prisma/build/index.js:284:116)
    at iWe (/my-app/node_modules/prisma/build/index.js:284:269)
Error: Command failed with exit code 1: /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version
/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
    at YIe (/my-app/node_modules/prisma/build/index.js:5:57)
    at /my-app/node_modules/prisma/build/index.js:5:10625
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async iWe (/my-app/node_modules/prisma/build/index.js:284:343) {
  shortMessage: 'Command failed with exit code 1: /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
  command: '/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x --version',
  escapedCommand: '"/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x" --version',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: "/my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x: /lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /my-app/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)",
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
prisma                  : 5.19.0-dev.8
@prisma/client          : 5.18.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.18.2
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at ../node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : E_CANNOT_RESOLVE_VERSION (at ../node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.19.0-12.ae18f9165678fc6c7b7b107340ca0435be434765
Default Engines Hash    : ae18f9165678fc6c7b7b107340ca0435be434765
Studio                  : 0.502.0
Preview Features        : omitApi

briangottfried · 2024-09-01T00:49:39Z

Just upgraded to 5.19.0, I am getting a similar error (using nix)

PrismaClientInitializationError: Unable to require(`/runner/_work/app/app/libs/api/db/generated/client/libquery_engine-debian-openssl-1.1.x.so.node`).
  Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.

Details: libssl.so.1.1: cannot open shared object file: No such file or directory
    clientVersion: '5.19.0',
    errorCode: undefined
  }

`DEBUG="prisma:get-platform" npx prisma --version`

prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +362ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +1ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +1ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
Environment variables loaded from .env
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +593ms
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu") +0ms
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.1.1 +1ms
prisma:get-platform The parsed libssl version is: 1.1.x +1ms
Error: Unable to require(`/runner/_work/app/app/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.
Details: libssl.so.1.1: cannot open shared object file: No such file or directory
    at pne (/runner/_work/app/app/node_modules/prisma/build/index.js:284:116)
    at lWe (/runner/_work/app/app/node_modules/prisma/build/index.js:284:269)
prisma                  : 5.19.0
@prisma/client          : 5.19.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.20.2
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : schema-engine-cli 5fe21811a6ba0b952a3bc7[140] 0666511fe3b902f (at node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b902f
Default Engines Hash    : 5fe21811a6ba0b952a3bc71400666511fe3b902f
Studio                  : 0.502.0

Schema

generator client {
  provider        = "prisma-client-js"
  output          = "../generated/client"
  previewFeatures = ["prismaSchemaFolder", "typedSql"]
}

jkomyno · 2024-09-02T10:42:24Z

Hi @mathiasayivor, thanks for confirming that prisma@5.19.0-dev.7 works for you!
Now let's try to understand why we got this problem in the first place.

In https://github.com/prisma/ecosystem-tests/tree/dev/docker/ubuntu-22.04-amd64-openssl-3.0.x, we test that on Ubuntu 22.04 on x64, the default engine target for Prisma is debian-openssl-3.0.x, as libssl.so.3 is found in /lib/x86_64-linux-gnu/ (see in Dockerfile).

As no official node Docker image is distributed using ubuntu base image, our testing setup for this specific scenario is roughly as follows:

use ubuntu:22.04 as a base image (source)
install Node.js (in our case, 18.12.0) via apt (source)
check for libssl detection
check that prisma --version matches the debian-openssl-3.0.x binary target

Now the question is: how can we reproduce your and @satadhi's setup in a Dockerfile? We kindly need your help here to avoid similar regressions in the future. Thanks!

aqrln · 2024-09-02T10:52:25Z

@jkomyno I believe the way to reproduce would be to install the libssl1.1 package

apolanc · 2024-09-02T15:09:42Z

This should be fixed in the 5.19.1 version, closing this now.

briangottfried · 2024-09-02T16:59:53Z

This is actually still sad for me

PrismaClientInitializationError: Unable to require(`/runner/_work/app/libs/db/generated/client/libquery_engine-debian-openssl-1.1.x.so.node`).
  Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.
  Details: libssl.so.1.1: cannot open shared object file: No such file or directory
      at Object.loadLibrary (/runner/_work/app/dist/apps/app/api/main.js:2796:15)
      at async Cr.loadEngine (/runner/_work/app/dist/apps/app/api/main.js:2838:56)
      at async Cr.instantiateLibrary (/runner/_work/app/dist/apps/app/api/main.js:2818:113) {
    clientVersion: '5.19.1',
    errorCode: undefined
  }

aqrln · 2024-09-02T17:01:46Z

@briangottfried did you re-generate the client after updating Prisma?

aqrln · 2024-09-02T17:03:02Z

also this looks a different error than what people in this issue have been facing

satadhi added the kind/bug A reported bug. label Aug 28, 2024

github-staff deleted a comment from satadhi Aug 28, 2024

jkomyno changed the title ~~Version 5.19.0 appears broken~~ [regression] Schema engine error in Prisma 5.19.0 Aug 28, 2024

jkomyno added the bug/1-unconfirmed Bug should have enough information for reproduction, but confirmation has not happened yet. label Aug 28, 2024

jkomyno added the domain/schema Issue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc. label Aug 28, 2024

apolanc added the kind/regression A reported bug in functionality that used to work before. label Aug 29, 2024

jkomyno mentioned this issue Sep 2, 2024

Revert "chore(deps): bump openssl from 0.10.60 to 0.10.66" prisma/prisma-engines#4995

Merged

1 task

apolanc closed this as completed Sep 2, 2024

lryanle mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.12.0 to 5.19.1 lryanle/SMARE#333

Open

laravel2004 mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.19.1 laravel2004/backend-peqing#5

Open

itscharukadeshan mentioned this issue Sep 24, 2024

[Snyk] Upgrade prisma from 5.19.0 to 5.19.1 itscharukadeshan/ClipThread-API#63

Merged

cibedex mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.1.1 to 5.19.1 cibedex/slax#1

Open

Erik-EFL mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.11.0 to 5.19.1 Erik-EFL/filaCommand#9

Open

pshaddel mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.19.1 pshaddel/ts-express-prisma#96

Closed

Jamesp918 mentioned this issue Sep 24, 2024

[Snyk] Upgrade @prisma/client from 5.18.0 to 5.19.1 Callgent/callgent-api#72

Open

Jamesp918 mentioned this issue Sep 25, 2024

[Snyk] Upgrade @prisma/client from 5.18.0 to 5.19.1 Callgent/callgent-api#75

Open

This was referenced Sep 29, 2024

[Snyk] Upgrade @prisma/client from 5.13.0 to 5.19.1 JerryJ1964/desktop-tutorial#2

Open

[Snyk] Upgrade @prisma/client from 5.13.0 to 5.19.1 JerryJ1964/desktop-tutorial#6

Open

origranot mentioned this issue Oct 2, 2024

[Snyk] Upgrade @prisma/client from 5.17.0 to 5.19.1 origranot/reduced.to#866

Closed

KeeghanM mentioned this issue Oct 3, 2024

[Snyk] Upgrade @prisma/client from 5.18.0 to 5.19.1 KeeghanM/chess-training-app-2.0#95

Merged

davidebukali mentioned this issue Oct 3, 2024

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.19.1 davidebukali/ai-powered-nextjs-app#1

Open

samir-141 mentioned this issue Oct 3, 2024

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.19.1 crissttofer/software#5

Open

vigneshshettyin mentioned this issue Oct 3, 2024

[Snyk] Upgrade prisma from 5.18.0 to 5.19.1 vigneshshettyin/EatMyURL#203

Merged

yashanand167 mentioned this issue Oct 5, 2024

[Snyk] Upgrade @prisma/client from 5.16.1 to 5.19.1 yashanand167/Insta-Clone-Backend#1

Merged

Bidaya0 mentioned this issue Oct 13, 2024

[Snyk] Upgrade prisma from 5.17.0 to 5.19.1 Bidaya0/litellm#1

Open

harundarat mentioned this issue Oct 16, 2024

[Snyk] Upgrade @prisma/client from 5.18.0 to 5.20.0 harundarat/express-layered-architecture#3

Open

yashanand167 mentioned this issue Oct 25, 2024

[Snyk] Upgrade @prisma/client from 5.19.1 to 5.20.0 yashanand167/Insta-Clone-Backend#5

Merged

origranot mentioned this issue Oct 25, 2024

[Snyk] Upgrade @prisma/client from 5.17.0 to 5.20.0 origranot/reduced.to#875

Closed

0xlynix mentioned this issue Oct 26, 2024

[Snyk] Upgrade @prisma/client from 5.10.2 to 5.20.0 0xlynix/lynixca#1

Open

This was referenced Oct 27, 2024

[Snyk] Upgrade @prisma/client from 5.19.1 to 5.20.0 vigneshshettyin/EatMyURL#216

Merged

[Snyk] Upgrade prisma from 5.19.1 to 5.20.0 vigneshshettyin/EatMyURL#217

Merged

folkmoz mentioned this issue Nov 5, 2024

[Snyk] Upgrade @prisma/client from 5.7.0 to 5.20.0 folkmoz/folkmoz-roommatch#70

Open

deployor mentioned this issue Nov 5, 2024

[Snyk] Upgrade @prisma/client from 5.19.1 to 5.21.0 deployor/tovy#1

Open

pshaddel mentioned this issue Nov 6, 2024

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.21.0 pshaddel/ts-express-prisma#101

Closed

ajile-in mentioned this issue Nov 6, 2024

[Snyk] Upgrade @prisma/client from 5.1.1 to 5.21.0 credebl/platform#1062

Open

0xlynix mentioned this issue Nov 9, 2024

[Snyk] Upgrade @prisma/client from 5.10.2 to 5.21.1 0xlynix/lynixca#6

Open

folkmoz mentioned this issue Nov 12, 2024

[Snyk] Upgrade @prisma/client from 5.7.0 to 5.21.1 folkmoz/folkmoz-roommatch#72

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[regression] `Schema engine error` in Prisma 5.19.0 #25101

[regression] `Schema engine error` in Prisma 5.19.0 #25101

satadhi commented Aug 28, 2024

callumJPritchard commented Aug 28, 2024

satadhi commented Aug 28, 2024 •

edited

Loading

jkomyno commented Aug 28, 2024

jkomyno commented Aug 28, 2024

satadhi commented Aug 28, 2024 •

edited

Loading

aqrln commented Aug 28, 2024

satadhi commented Aug 28, 2024

satadhi commented Aug 28, 2024

aqrln commented Aug 28, 2024

aqrln commented Aug 28, 2024

satadhi commented Aug 28, 2024

mathiasayivor commented Aug 31, 2024

jkomyno commented Aug 31, 2024

mathiasayivor commented Aug 31, 2024

briangottfried commented Sep 1, 2024

jkomyno commented Sep 2, 2024

aqrln commented Sep 2, 2024

apolanc commented Sep 2, 2024 •

edited

Loading

briangottfried commented Sep 2, 2024

aqrln commented Sep 2, 2024

aqrln commented Sep 2, 2024

[regression] Schema engine error in Prisma 5.19.0 #25101

[regression] Schema engine error in Prisma 5.19.0 #25101

Comments

satadhi commented Aug 28, 2024

Bug description

How to reproduce

Expected behavior

Prisma information

Environment & setup

Prisma Version

callumJPritchard commented Aug 28, 2024

satadhi commented Aug 28, 2024 • edited Loading

jkomyno commented Aug 28, 2024

jkomyno commented Aug 28, 2024

satadhi commented Aug 28, 2024 • edited Loading

aqrln commented Aug 28, 2024

satadhi commented Aug 28, 2024

satadhi commented Aug 28, 2024

aqrln commented Aug 28, 2024

aqrln commented Aug 28, 2024

satadhi commented Aug 28, 2024

mathiasayivor commented Aug 31, 2024

jkomyno commented Aug 31, 2024

mathiasayivor commented Aug 31, 2024

CMD: yarn prisma db push

prisma@5.19.0-dev.7:

prisma@5.19.0-dev.8:

CMD: DEBUG="prisma:get-platform" prisma --version

prisma@5.19.0-dev.7:

prisma@5.19.0-dev.8:

briangottfried commented Sep 1, 2024

DEBUG="prisma:get-platform" npx prisma --version

Schema

jkomyno commented Sep 2, 2024

aqrln commented Sep 2, 2024

apolanc commented Sep 2, 2024 • edited Loading

briangottfried commented Sep 2, 2024

aqrln commented Sep 2, 2024

aqrln commented Sep 2, 2024

[regression] `Schema engine error` in Prisma 5.19.0 #25101

[regression] `Schema engine error` in Prisma 5.19.0 #25101

satadhi commented Aug 28, 2024 •

edited

Loading

satadhi commented Aug 28, 2024 •

edited

Loading

`DEBUG="prisma:get-platform" npx prisma --version`

apolanc commented Sep 2, 2024 •

edited

Loading