-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Get config: Unable to establish a connection to query-engine-node-api library #13717
Comments
Error message is from our new error reporting code from @jkomyno:
|
To confirm: |
I got this error when using 3.14.0 and 3.13.0 I'm also using Ubuntu 22.04 |
i confirm using version 3.13.x 3.14.x gives this error
when using 3.15 gives the Config Error described above. in bouth cases making prisma work on ubuntu 22.04 is not possible. |
@irfanabdnst Please create a new issue providing all the info the bug issue template asks for. Thanks. |
Looks like you are using snap to either install Node.js or openssl or maybe even glibC. Since snaps are sandboxes we can't dynamically link to required runtime libraries and so it will throw out that error. So please try installing these libs using
If that doesn't work, install node.js via a version manager like fnm or use apt(https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions) |
https://github.com/nodesource/distributions/blob/master/README.md # Using Ubuntu
curl -fsSL https://deb.nodesource.com/setup_16.x | sudo -E bash -
sudo apt-get install -y nodejs Ok the snap version of node is not compatible with prisma. |
We want to keep this open for the bug with the error reporting that you also reported. Thanks for your help in confirming that this was caused by the snap thingie. |
Hi @PiecePaperCode, to summarise, this issue was due an incompatibility between your system's snap, as highlighted in this comment. Tomorrow we will release a new major version that will contain improvements such as the following error message that tries to explain which connecting to the
Please let us know if we can close this issue then :) |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I still have this issue, which new version can fix it?
|
There is no new version that can fix this, as this is a problem on your system. See the instructions on how to fix here: #13717 (comment) |
$ npm-run-all build-tracker build-geo build-db build-app tracker/index.js → public/umami.js... Error: Cannot find module 'fs-extra'
|
Prisma schema loaded from prisma\schema.prisma Prisma CLI Version : 3.15.2 |
It turns out that cannot generate scheme without root permission in linux. I finally can generate it with root. I don't know how to make it work without root permission. |
@aniwn88480857 Your first post looks completely unrelated to Prisma. Your second one is an old version that does not show the full error message, please upgrade to Prisma 4.0.0. @shtse8 That is not a known limitation, and probably has to do with how you installed your node or application. If the error persists, please open a discussion here in Github and provide more information so Support can take a look. Thanks. |
Having an issue with prisma on a new laptop ubuntu 22.04
I checked my node.js is not installed via snap, instead installed via nvm whereis node whereis openssl any ideas? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Same issue in Docker
If someone finds a solution for Alpine images – please share. |
@ivan-kleshnin There should be further output with the actual error message that provides the details what is going wrong in your case. |
@janpio here's the rest of the message, thank you for responding:
|
Ugh, that one is new. Can you please open a new issue for this and fill the full template? We should try to reproduce this and understand what exactly is going on. |
i was having this simple problem, >>> sudo su npx migrate dev.... |
While I don't have a template for you unfortunately, I was encountering this error in my CI. In my project, I build a docker image using For my runner layer, I was using I hope this gives you some more detail! |
M1 mac @ivan-kleshnin - I am using a similar dockerfile to you, are you using caches in your build at all? FROM node:16.13-alpine AS deps
....
RUN apk add --update libc6-compat openssl openssl-dev
...
RUN npx prisma generate when I change the platform with the following command, the build runs fine, prisma working as expected in the running image docker buildx build --platform linux/amd64 -t t3-docker-remote . However, running this natively just gives me the linking issue described elsewhere in this thread. Not perfect, but a workaround. docker build --no-cache --progress plain -t t3-docker .
...
===
#18 [builder 7/8] RUN npx prisma generate
#18 sha256:c7637aa50432c0c2d8ea90a90427e815ffa0054831571436cc5760b182addbd8
#18 0.712 Error: Unknown binaryTarget linux-arm64-openssl-undefined and no custom engine files were provided |
Please open new issues with additional information if you still encounter this problem. Thanks. |
$/prisma/starter$ npx prisma generate Prisma schema loaded from prisma/schema.prisma Error: Get config: Unable to establish a connection to query-engine-node-api library Prisma CLI Version : 3.15.1-dev.1
How to Reproduce
OS: 22.04 Ubuntu
Node: 16.15.1
Follow these instructions. https://www.prisma.io/docs/getting-started/quickstart#1-download-the-starter-project
Switch to latest possible release: 3.15.1-dev.1 as per today.
What have i tried so far
Switching databases sqlite, postgres
Switching node from 16 to 17.
using 3.13 3.14 gives me this error
in ubuntu i could not figure out how to install GLIBC_2.33
tying with npm and yarn
The text was updated successfully, but these errors were encountered: