No 'uwsgi_python' executable found in $PATH

[Wesley-Li]

Hi guys,
Today I am trying to install critic on my Centos6.5 desktop.
It always raises uwsgi_python error...

Actuall, I installed uwsgi and can run uwsgi from command line， e.g.
[root@android critic]# uwsgi --version
2.0.14
[root@android critic]#

So, what's wrong here? Anyone hit this before?
Thanks.
Wesley

[jensl]

On Ubuntu, the uwsgi_python executable comes from the package uwsgi-plugin-python, and isn't installed by just installing the base uwsgi package. Maybe the situation is similar on Centos?

[Wesley-Li]

I don't know exactly, but , I also run other web service on the same desktop with nginx+uwsgi+python, everything is OK for other web service.

[jensl]

Alright. So maybe on Centos the uwsgi_python executable isn't in the search path, then. I guess the important thing really is that the uwsgi binary is, and that it can find uwsgi_python. Temporarily adjusting the search path while running Critic's installation script should be a viable workaround in that case.

Or maybe the Python support is compiled into the uwsgi binary somehow and not a separate plugin at all. In that case, I suppose the problem is that Critic's check for properly installed uWSGI (with Python support) is simply broken. A better one might be to run uwsgi --need-plugin python --version it seems; that just prints the version if the plugin is available, and fails if not.

Can you check if there is a uwsgi_python executable anywhere on your system, and if not, check whether that --need-plugin command succeeds?

[Wesley-Li]

[root@android admin]# uwsgi --need-plugin python --version
open("./python_plugin.so"): No such file or directory [core/utils.c line 3684]
!!! UNABLE to load uWSGI plugin: ./python_plugin.so: cannot open shared object file: No such file or directory !!!
unable to load plugin "python"
[root@android admin]#

And, no executable uwsgi_python within system...

[jensl]

To me it looks like the Python support just isn't there. Critic is designed to run with the python plugin, which by the looks of it isn't available. So the check for Python support (by looking for the uwsgi_python executable) would appear to fail quite correctly.

I'm in no way an expert at uWSGI though, so I might be misunderstanding things. But if running uwsgi --plugin python ... fails, then the application configuration file that the installation script would generate most likely would fail too. If there's some other way to run Python code through uWSGI, Critic doesn't support it.

[mattiasb]

Late reply, but I'm pretty sure this is remedied by installing uwsgi-plugin-python.