Problem: .so(shared object) as library in python works well when
python calls it and fails in uWSGI-running python(Django) application.
More info: I've build Go module with
go build -buildmode=c-shared -o output.so input.go to call it in Python with
from ctypes import cdll lib = cdll.LoadLibrary('path_to_library/output.so')
When django project is served via uWSGI the request handler that calling Go library freezes, causing future 504 in Nginx. After getting in "so called freeze", uWSGI is locked there and only restarting helps to enliven app. No logs AT ALL! It just freezes.
Everything works correctly when i run in python interpreter on the same machine.
My thoughts: i've tried to debug this and put a lot of log messages in library, but it won't give much info because everything is fine with library(because it works in interpreter). Library loads correctly, because some log messages that i've putted in library. I think it some sort of uWSGI limitation. I don't think putting uwsgi.ini file is somehow helpful.
OS: CentOS 6.9
Python: Python 3.6.2
What limitations can be in uWSGI in that type of shared object work and if there a way to overcome them?