-
Notifications
You must be signed in to change notification settings - Fork 32
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
[BUG] : undefined symbol: EVP_PKEY_base_id
(in mgclient.cpython-39-x86_64-linux-gnu.so
)
#285
Comments
Hi @Tim-K-DFW, can you try |
Hi Katarina, thank you for the quick response!
|
Did you experience any issues when installing with pip? |
|
Can you remove that installation, install all necessary prerequisites for GQLAlchemy (that is, pymgclient) and then try reinstalling it? |
I did:
Same result:
|
I think that might be related to the mismatch of the OpenSSL version. Can you tell me which version you have? |
Are you sure that conda env uses that OpenSSL by default? This reminds me of the closed issue on the pymgclient repository. |
Do you happen to know how I can check this? |
Can you try installing the pymgclient prerequisites in conda env with pip? The steps in conda env would be:
|
|
My mistake on |
Can you try installing gqlalchemy without conda, to verify the assumption? |
YES! In vanilla python, it's importing with no issues. This has to be some Conda stuff. Thank you so much! |
No problem, I'm glad to help and happy it's working for you now! I will leave this issue open to resolve conda issues 😄 |
Investigated the issue, you are probably having locally old version of pymgclient. Clean pymgclient from global path (pip uninstall pymgclient gqlalchemy), activate your conda environmen and install ONLY gqlalchemy (pip install gqlalchemy). You should see that pymgclient 1.3.1 is being built while installing gqlalchemy. No need to install pymgclient before gqlalchemy, we have wrong instructions in README, we will fix it. |
@Tim-K-DFW let us know if you decide to try out Conda env again and verify if what @as51340 provided fixes the issue 😄 Thanks! |
Memgraph version
v2.11.0
Environment
pip install gqlalchemy
)docker run --name memgraph -p 7687:7687 -p 7444:7444 -p 3000:3000 memgraph/memgraph-platform
)Describe the bug
Fail to import, see log below; same thing happens whether memgraph is running or not.
To Reproduce
import gqlalchemy
Expected behavior
To import.
Logs
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: