Railway•3y ago

13 4.188 Error Unable to establish a connection to query-engine-node-api library.

Has anyone encountered this before? It occurs during the build step on railway and doesn't occur locally: https://github.com/prisma/prisma/issues/14073 maybe?

#13 1.556 > npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json
#13 1.556
 
#13 2.070 npm WARN config production Use `--omit=dev` instead.
 
#13 3.788 Prisma schema loaded from prisma/schema.prisma
 
#13 4.188 Error: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
#13 4.188 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`)
#13 4.188  libssl.so.1.1: cannot open shared object file: No such file or directory
#13 4.188 [Context: getConfig]
 
#13 4.188
#13 4.188 Prisma CLI Version : 4.3.1
 
#13 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1

#13 1.556 > npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json
#13 1.556
 
#13 2.070 npm WARN config production Use `--omit=dev` instead.
 
#13 3.788 Prisma schema loaded from prisma/schema.prisma
 
#13 4.188 Error: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
#13 4.188 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`)
#13 4.188  libssl.so.1.1: cannot open shared object file: No such file or directory
#13 4.188 [Context: getConfig]
 
#13 4.188
#13 4.188 Prisma CLI Version : 4.3.1
 
#13 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1

GitHub

Unable to establish a connection to query-engine-node-api library. ...

Bug description Error: Get Config: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation! Details: Unable to require(`/home/f...

37 Replies

Unknown User•3y ago

Message Not Public

HarrisOP•3y ago

no luck unfortunately

Unknown User•3y ago

Message Not Public

HarrisOP•3y ago

same issue

HarrisOP•3y ago

HarrisOP•3y ago

just making sure, this is the right place for the variable?

Unknown User•3y ago

Message Not Public

HarrisOP•3y ago

#14 [stage-0 10/10] RUN --mount=type=cache,id=s/993173be-02c7-4a4e-93b6-815c345c6650-node_modules/cache,target=node_modules/.cache npm run build
#14 sha256:994b00f244c797d3eaa33cc1406dccf8466f6131100dbc6b81b21aa4b231453c
 
#14 1.451 npm
WARN config production Use `--omit=dev` instead.
#14 1.466
#14 1.466 > [email protected] build
#14 1.466 > npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json
#14 1.466
 
#14 1.854 npm
WARN config production Use `--omit=dev` instead.
 
#14 3.442 Prisma schema loaded from prisma/schema.prisma
 
#14 3.854 Error: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
#14 3.854 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`)
#14 3.854  libssl.so.1.1: cannot open shared object file: No such file or directory
#14 3.854 [Context: getConfig]
#14 3.854
#14 3.854 Prisma CLI Version : 4.3.1
 
#14 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1
-----
> [stage-0 10/10] RUN --mount=type=cache,id=s/993173be-02c7-4a4e-93b6-815c345c6650-node_modules/cache,target=node_modules/.cache npm run build:
-----
 
executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1
 
Error: Docker build failed

#14 [stage-0 10/10] RUN --mount=type=cache,id=s/993173be-02c7-4a4e-93b6-815c345c6650-node_modules/cache,target=node_modules/.cache npm run build
#14 sha256:994b00f244c797d3eaa33cc1406dccf8466f6131100dbc6b81b21aa4b231453c
 
#14 1.451 npm
WARN config production Use `--omit=dev` instead.
#14 1.466
#14 1.466 > [email protected] build
#14 1.466 > npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json
#14 1.466
 
#14 1.854 npm
WARN config production Use `--omit=dev` instead.
 
#14 3.442 Prisma schema loaded from prisma/schema.prisma
 
#14 3.854 Error: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
#14 3.854 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`)
#14 3.854  libssl.so.1.1: cannot open shared object file: No such file or directory
#14 3.854 [Context: getConfig]
#14 3.854
#14 3.854 Prisma CLI Version : 4.3.1
 
#14 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1
-----
> [stage-0 10/10] RUN --mount=type=cache,id=s/993173be-02c7-4a4e-93b6-815c345c6650-node_modules/cache,target=node_modules/.cache npm run build:
-----
 
executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1
 
Error: Docker build failed

Unknown User•3y ago

Message Not Public

HarrisOP•3y ago

I'd appreciate it, I'm super rusty with Dockerfiles. I'm confused, what caused the change? Up until this morning I didn't have this issue

jr•3y ago

What version of prisma and node are you using? Can you share a project id or a repo?

HarrisOP•3y ago

{
    "name": "discordbot",
    "version": "0.0.1",
    "description": "Discord bot for Ember AI's conversational agent",
    "main": "./dist/index.js",
    "scripts": {
        "start": "npm run build && node .",
        "build": "npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json",
        "generate": "npx prisma generate"
    },
    "author": "Harris Rothaermel",
    "license": "ISC",
    "dependencies": {
        "@discordjs/rest": "^1.1.0",
        "@prisma/client": "^4.3.1",
        "async-retry": "^1.3.3",
        "cors": "^2.8.5",
        "discord.js": "^14.3.0",
        "dotenv": "^16.0.2",
        "express": "^4.18.1",
        "openai": "^3.0.0"
    },
    "devDependencies": {
        "@types/async-retry": "^1.4.5",
        "@types/cors": "^2.8.12",
        "@types/express": "^4.17.14",
        "@types/node": "^18.7.16",
        "eslint": "^8.23.0",
        "prisma": "^4.3.1",
        "typescript": "^4.8.2"
    }
}

{
    "name": "discordbot",
    "version": "0.0.1",
    "description": "Discord bot for Ember AI's conversational agent",
    "main": "./dist/index.js",
    "scripts": {
        "start": "npm run build && node .",
        "build": "npx prisma generate && npx prisma migrate deploy && rimraf dist && tsc -p tsconfig.json",
        "generate": "npx prisma generate"
    },
    "author": "Harris Rothaermel",
    "license": "ISC",
    "dependencies": {
        "@discordjs/rest": "^1.1.0",
        "@prisma/client": "^4.3.1",
        "async-retry": "^1.3.3",
        "cors": "^2.8.5",
        "discord.js": "^14.3.0",
        "dotenv": "^16.0.2",
        "express": "^4.18.1",
        "openai": "^3.0.0"
    },
    "devDependencies": {
        "@types/async-retry": "^1.4.5",
        "@types/cors": "^2.8.12",
        "@types/express": "^4.17.14",
        "@types/node": "^18.7.16",
        "eslint": "^8.23.0",
        "prisma": "^4.3.1",
        "typescript": "^4.8.2"
    }
}

Unknown User•3y ago

Message Not Public

HarrisOP•3y ago

Node version locally is: v18.9.0

jr•3y ago

project id?

HarrisOP•3y ago

Is that a railway id? Where can I find that?

jr•3y ago

just a link to the deployment will work

HarrisOP•3y ago

https://railway.app/project/c7dbb1b2-e574-4cb8-8761-d3f78a9bd658/service/993173be-02c7-4a4e-93b6-815c345c6650?id=8c01127b-9b1b-43f6-8bed-c041fb15753a

jr•3y ago

I think the problem is that it is being built with node 16. Can you add

"engines": {
  "node": "18.x"
}

"engines": {
  "node": "18.x"
}

to you package.json as well as the variable NIXPACKS_PKGS=openssl (and remove the NIXPACKS_APT_PKGS variable)

HarrisOP•3y ago

pushed, and currently building now, will report back

jr•3y ago

It might still error. I'm trying some things. I am unsure what is up with this prisma

HarrisOP•3y ago

Fixed the error, although I have a new one now

#13 2.594 Prisma schema loaded from prisma/schema.prisma
 
#13 3.885
#13 3.885 ✔ Generated Prisma Client (4.3.1 | library) to ./node_modules/@prisma/client in 204ms
#13 3.885 You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
#13 3.885 
#13 3.885 import { PrismaClient } from '@prisma/client'
#13 3.885 const prisma = new PrismaClient()
#13 3.885 
 
#13 4.380 npm WARN config production Use `--omit=dev` instead.
 
#13 5.831 Prisma schema loaded from prisma/schema.prisma
 
#13 5.876 Datasource "db": PostgreSQL database "railway", schema "public" at "containers-us-west-84.railway.app:5557"
#13 5.953
 
#13 5.953 Error: Migration engine error:
#13 5.953
 
#13 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1

#13 2.594 Prisma schema loaded from prisma/schema.prisma
 
#13 3.885
#13 3.885 ✔ Generated Prisma Client (4.3.1 | library) to ./node_modules/@prisma/client in 204ms
#13 3.885 You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
#13 3.885 
#13 3.885 import { PrismaClient } from '@prisma/client'
#13 3.885 const prisma = new PrismaClient()
#13 3.885 
 
#13 4.380 npm WARN config production Use `--omit=dev` instead.
 
#13 5.831 Prisma schema loaded from prisma/schema.prisma
 
#13 5.876 Datasource "db": PostgreSQL database "railway", schema "public" at "containers-us-west-84.railway.app:5557"
#13 5.953
 
#13 5.953 Error: Migration engine error:
#13 5.953
 
#13 ERROR: executor failed running [/bin/bash -ol pipefail -c npm run build]: exit code: 1

jr•3y ago

very strange. I am checking

HarrisOP•3y ago

I checked my prisma migrate command and it told me no changes have been found, not quite sure what it's referring to in the error

❯ npx prisma migrate dev --name Update migrations
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "harris", schema "public" at "localhost:5432"

Already in sync, no schema change or pending migration was found.

✔ Generated Prisma Client (4.3.1 | library) to ./node_mod
ules/@prisma/client in 78ms

❯ npx prisma migrate dev --name Update migrations
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "harris", schema "public" at "localhost:5432"

Already in sync, no schema change or pending migration was found.

✔ Generated Prisma Client (4.3.1 | library) to ./node_mod
ules/@prisma/client in 78ms

^ locally

jr•3y ago

I see that you have successful build from 2 days ago. What has changed since then?

HarrisOP•3y ago

That's what I'm confused about, I don't know what I've changed since then that would cause issues

HarrisOP•3y ago

HarrisOP•3y ago

HarrisOP•3y ago

All I changed between the working and non working deployments

jr•3y ago

Can you try deploying again

HarrisOP•3y ago

oh weird i dunno what happened but I can't get to my railway dashboard at all right now

HarrisOP•3y ago

Unknown User•3y ago

Message Not Public

jr•3y ago

Can you DM me your public IP address please

HarrisOP•3y ago

went ahead and redeployed, will see if there are any changes

jr•3y ago

Looks like it built and deployed okay? I beleive an update to nixpacks broke something with openssl. Taking a deeper look now, but it should be good to go on railway

HarrisOP•3y ago

just in time too! I had a call where I did a live demo of something (i had completely forgotten we were having deploy issues)

Gaming

Programming

13 4.188 Error Unable to establish a connection to query-engine-node-api library.