Control: forwarded -1 https://github.com/asciimoo/searx/issues/929
Hi Thomas, On Fri, 25 May 2018 11:40:28 -0400 Thomas Ward <[email protected]> wrote: > During testing of observed downstream autopkgtest failures in Ubuntu, the > `searx` package fails to run under uWSGI, which its upstream documentation > says to utilize. The crash error is absorbed by uWSGI and processed as a > segmentation fault in uWSGI. > > While `searx` can be run directly, it complains saying you should run > production deployments of searx via WSGI. When attempting to run it in > uWSGI (which the CI tests and downstream autopkgtests do), it causes a > segmentation fault in uWSGI during CI tests, and a continual "Failed to > load application" loop in uWSGI when uwsgi is run directly by superuser. > > Looking at the Debian CI logs, this has been failing since April 29th. > This was noticed downstream due to the failures in the autopkgtests > blocking uwsgi and nginx from migrating (because the CI test for searx > uses nginx). > > Please either fix the autopkgtests and uwsgi integration, or try > switching your tests to an Apache-based WSGI-module execution to avoid > package failures. thanks for reporting this! As of now I didn't find the cause for this issue, because uwsgi fails before it writes any logs. This seems to be the following upstream bug: https://github.com/asciimoo/searx/issues/929 Thanks! cheers, josch
signature.asc
Description: signature
