Error when importing Aerospike
See original GitHub issueWhen trying to import Aerospike Python Client (v3.4.1) using Python 3.6.5 in a VirtualEnv (using Linux Mint 19) I’m getting this error message;
ImportError: /opt/pyenv/apisd/lib/python3.6/site-packages/aerospike.cpython-36m-x86_64-linux-gnu.so: undefined symbol: SSLv23_client_method
I’ve already tried this solution https://github.com/aerospike/aerospike-client-python/issues/214 and it isn’t working 😕
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Unable to import aerospike in python 3.7 - Stack Overflow
I was trying to import aerospike after downloading it using pip and I am getting this error. I tried reinstalling the python using...
Read more >Python client error when doing import
I am on a Macbook, Yosemite with lua51 installed via brew. I did pip install. However I cant get the client to load....
Read more >Aerospike Exceptions
import aerospike from aerospike import exception as ex try: config = { 'hosts': ... AerospikeError as e: print("Error: {0} [{1}]".format(e.msg, e.code)).
Read more >Basic error handling in spring-data-aerospike - Medium
Basic error handling in spring-data-aerospike. Everything fails all the time. ... import org.springframework.retry.annotation.Backoff;
Read more >[Example code]-Unable to import aerospike in python 3.7
The Aerospike python client is most likely failing on import because of a missing openssl dependency. I would recommend installing openssl brew install...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok. I forgot that the Python client version 3.4.1 depends on the C client version 4.3.14 . So for now, to get that to work, it’s necessary to build the C client at the tagged version 4.3.14 . e.g. From the C client directory
This is a lot of steps, and we’re working to make it simpler.
The next version of the Python client (3.4.2) works with the newest C client, so once that gets released on Pypi, which should be today or early next week, the solution mentioned in #214 should work.
Thanks for bringing up the issue!
any chance to get this issue solved in a better way? like, push 2 different versions to pip repo? we use erogenous environments, ubuntu 18.04, arch, latest fedora to build and develop our product, this issue makes the dependency maintenance much more complicated then he need to be… Thanks,