Skip to content
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

Prisma on linux #2

Closed
sorenbs opened this issue Jun 20, 2019 · 19 comments
Closed

Prisma on linux #2

sorenbs opened this issue Jun 20, 2019 · 19 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Milestone

Comments

@sorenbs
Copy link
Member

sorenbs commented Jun 20, 2019

libssl1.1.so is missing

@sorenbs
Copy link
Member Author

sorenbs commented Jun 21, 2019

Reported by Al Str in Slack:

Hello, I installed the newer openssl version required by prisma. There are some tutorial on the web (keep attention, the lib need to be shared) But prisma2 has another required library glibc 2.18 (centos has 2.17-260) and seems this cannot be upgraded because is a core part of the whole centos system. This upgrade will cause a "non booting" system.

Currently I don't think there is a possibility to run prisma2 with centos.

@dpetrick dpetrick changed the title Prisma on linux: libssl1.1.so is missing Prisma on linux Jun 24, 2019
@matthewmueller matthewmueller added this to the Prisma 2 GA milestone Jun 26, 2019
@matthewmueller matthewmueller added bug/2-confirmed Bug has been reproduced and confirmed. priority/high and removed bug labels Jun 27, 2019
@schickling schickling assigned dpetrick and timsuchanek and unassigned sorenbs Jun 28, 2019
@schickling schickling added team/product and removed team/engineering bug/2-confirmed Bug has been reproduced and confirmed. labels Jun 28, 2019
@schickling
Copy link
Member

Related: prisma/specs#2

@schickling schickling added bug/2-confirmed Bug has been reproduced and confirmed. team/engineering and removed team/product labels Jun 30, 2019
@timsuchanek timsuchanek added the kind/bug A reported bug. label Jul 2, 2019
@ansarizafar
Copy link

I am getting this error

image

@timsuchanek
Copy link
Contributor

@ansarizafar which linux distribution and version are you using?
Please share the result of uname -a

@ansarizafar
Copy link

ansarizafar commented Jul 15, 2019

uname -a
Linux home 4.4.0-151-generic #178-Ubuntu SMP Tue Jun 11 08:30:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I was having this issue previously prisma/migrate#19 but the issue was resolved
after installing recommended library libssl1.1

openssl version -a
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
platform: debian-amd64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
OPENSSLDIR: "/usr/lib/ssl"

@timsuchanek
Copy link
Contributor

Thanks a lot! So it sounds like it's solved for you now?
It looks like it's mostly a documentation issue around installing libssl.
Which steps (commands) did you take install libssl1.1?

@divyenduz
Copy link
Contributor

Closing this issue as it contains multiple issues, all of which are addressed except #157

If there is an issue with your distribution, please create a new issue with the specifics 🙏

nikolasburk pushed a commit that referenced this issue Aug 23, 2019
@tianhuil
Copy link

tianhuil commented Aug 30, 2019

I'm encountering this on Ubuntu 16. I get the following error on prisma2=2.0.0-preview-8 while running prisma2 init hello-prisma2:

DMMF To DML /home/vagrant/sql-speed/node_modules/prisma2/query-engine-linux-glibc-libssl1.0.2: /usr/lib/libssl.so.10: version `libss
l.so.10' not found (required by /home/vagrant/sql-speed/node_modules/prisma2/query-engine-linux-glibc-libssl1.0.2)

I followed the instructions here to avoid an earlier related error (it couldn't find /usr/lib/libssl.so.10). For your information:

$ uname -a
Linux michael2 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.6 LTS
Release:        16.04
Codename:       xenial

@divyenduz
Copy link
Contributor

@tianhuil Thanks for raising this, this was a known issue with ubuntu 16 that we fixed in preview 9
#157

Please update the CLI version/re-generate using prisma2 generate and try again.

I am closing this issue, please re-open a new issue if the problem persists for you and tag me on the new one.

🙌

@createvo
Copy link

createvo commented Oct 13, 2019

Hello,
I don't think this issue, started from my report in slack (Al Str), should be close.

CentOs 7.6.1810
Node 10.16.0
Linux devexp-01 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x
86_64 x86_64 GNU/Linux

I continued to have problems with glib library 2.18 because on centos there is 2.17 version installed.
My understanding is that the upgrade it is not safe for the server.

prisma2centos7

@pantharshit00
Copy link
Contributor

@createvo

Can you please give us more information about your OS like the version?

Output of uname -a would also be helpful.

I'd recommend you to open a new issue with the requested information

@createvo
Copy link

I edited my previous comment with the info. There was on slack.
Anyway yes, a new issue could be more helpful!
Thanks

SevInf added a commit that referenced this issue Jan 17, 2024
SevInf added a commit that referenced this issue Jan 18, 2024
* feat(adapter-pg,adapter-neon): Enforce usage of connection pool

Adapters don't work with non-pooled `Client` instances. For `pg` and
`neon` we enforce it only on type level, so check won't work for JS
projects. In this PR, we are checking the passed instance and ensuring
it is a `Pool`, similarly to what we already do for `planetscale`.

Fix prisma/team-orm#616

* Add test script

* Attempt to unify jest configs #2

* Fix couple of problems
SevInf added a commit that referenced this issue Jan 18, 2024
* feat(adapter-pg,adapter-neon): Enforce usage of connection pool

Adapters don't work with non-pooled `Client` instances. For `pg` and
`neon` we enforce it only on type level, so check won't work for JS
projects. In this PR, we are checking the passed instance and ensuring
it is a `Pool`, similarly to what we already do for `planetscale`.

Fix prisma/team-orm#616

* Add test script

* Attempt to unify jest configs #2

* Fix couple of problems
SevInf added a commit that referenced this issue Jan 18, 2024
…) (#22700)

* feat(adapter-pg,adapter-neon): Enforce usage of connection pool

Adapters don't work with non-pooled `Client` instances. For `pg` and
`neon` we enforce it only on type level, so check won't work for JS
projects. In this PR, we are checking the passed instance and ensuring
it is a `Pool`, similarly to what we already do for `planetscale`.

Fix prisma/team-orm#616

* Add test script

* Attempt to unify jest configs #2

* Fix couple of problems
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests