[uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread Glenn Reed
Hi, Hopefully someone can help me in something that should have a straightforward solution. I have tried install uwsgi multiple ways, including pip and apt-get. This is my ini file inside the vassals subdirectory: [uwsgi] chdir = /home/webquest/html/online.webquest.co.nz uid = webquest gid = we

Re: [uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread J. Pic
Look at what you have in /usr/lib/uwsgi/plugins/python* On some platforms, you want to load the python2 or python3 module, not simple python. If nothing is in /usr/lib/uwsgi/plugins/python* then you should install another package containing the python module. ___

Re: [uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread Glenn Reed
Thank you. Changing plugins = python to plugins = python3 seemed to remove that error but now I am seem to be getting no error but nginx is saying bad gateway (502 error). Here is the startup messages in full: webquest@wagtail1:~/vassals$ uwsgi --emperor ~/vassals/ *** Starting uWSGI 2.0.15-

Re: [uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread J. Pic
Nginx logs should know what is the next issue ;) ___ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Re: [uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread Glenn Reed
Turned out to be a socket permission problem. I had to use "chmod- socket = 666" on the socket. Is working now. :) On Thu, 2020-03-12 at 12:05 +1300, Glenn Reed wrote: > Thank you. Changing plugins = python to plugins = python3 seemed to > remove that error but now I am seem to be getting no e

Re: [uWSGI] uwsgi not recognising virtualenv option in ini file.

2020-03-11 Thread J. Pic
Excellent, have a lot of fun then ;) ___ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi