[Bug 247689] www/uwsgi: has the plugin embedded but doesn't work

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Jul 3 10:26:24 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247689

Newton Terry <newton.ja.terry at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |newton.ja.terry at gmail.com

--- Comment #6 from Newton Terry <newton.ja.terry at gmail.com> ---
I can reproduce the error. Current www/uwsgi, version 2.0.18, having set
plugins in configuration file, returns plugin error message when starting
service:

service uwsgi onestart

[uWSGI] getting INI configuration from /usr/local/etc/uwsgi/uwsgi.ini
!!! UNABLE to load uWSGI plugin: Cannot open "./router_redirect_plugin.so" !!!

/usr/local/etc/uwsgi/uwsgi.ini

[uwsgi]
plugins=router_redirect

In ports work-py37 directory no router_redirect_plugin.so is present. Recording
the build process with less verbosity (Makefile: #PYDISTUTILS_BUILDARGS=
--verbose) demonstrates the plugins are build embedded into the binary. From
the build log:

...
using profile: buildconf/default.ini

cut  ---------------------
work-py37/uwsgi-2.0.18/buildconf/default.ini
[uwsgi]
main_plugin = python,gevent
inherit = base

work-py37/uwsgi-2.0.18/buildconf/base.ini
[uwsgi]
...
embedded_plugins = %(main_plugin)s, ..., router_redirect,...

continue  ----------------

*** uWSGI compiling embedded plugins ***
...
[thread 4][cc] plugins/router_redirect/router_redirect.o
...

Also the build binary indicates having the plugins, inclusive
router_redirect_plugin, embedded:

strings /usr/local/bin/uwsgi | grep router_redirect
router_redirect_plugin
router_redirect

Updating the port to version 2.0.19.1 doesn't resolve, error message remains.

Attached:
uwsgi-2.0.18-build.log
uwsgi-2.0.19.1-build.log
uwsgi18-binary-embedd-plugins-list.txt
uwsgi19.1-binary-embedd-plugins-list.txt

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-python mailing list