Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Searx Doesn't Start Debian 10 #1670

Open
SubstituteR opened this issue Aug 6, 2019 · 0 comments

Comments

@SubstituteR
Copy link

commented Aug 6, 2019

After following the installation guide
https://asciimoo.github.io/searx/dev/install/installation.html
and confirming that everything works when starting searx manually with

python searx/webapp.py

And checking my nginx reverse proxy.
Doing it this way works 100%, however when I attempt to use uwsgi to demonize the process it doesn't actually start.
My uwsgi log shows

Tue Aug 6 04:10:59 2019 - added /usr/local/searx/ to pythonpath.
Tue Aug 6 04:10:59 2019 - spawned uWSGI master process (pid: 31839)
Tue Aug 6 04:10:59 2019 - spawned uWSGI worker 1 (pid: 31846, cores: 1)
Tue Aug 6 04:10:59 2019 - spawned uWSGI worker 2 (pid: 31847, cores: 1)
Tue Aug 6 04:10:59 2019 - spawned uWSGI worker 3 (pid: 31848, cores: 1)
Tue Aug 6 04:10:59 2019 - spawned uWSGI worker 4 (pid: 31850, cores: 1)
Tue Aug 6 04:11:01 2019 - WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x55def990df50 pid: 31846 (default app)
Tue Aug 6 04:11:01 2019 - WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x55def990df50 pid: 31848 (default app)
Tue Aug 6 04:11:01 2019 - WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x55def990df50 pid: 31847 (default app)
Tue Aug 6 04:11:01 2019 - WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x55def990df50 pid: 31850 (default app)

and my nginx error log shows

2019/08/06 04:10:13 [error] 31469#31469: *1 connect() failed (111: Connection refused) while connecting to upstream, client: {removed}, server: localhost, request: "GET /searx/ HTTP/1.1", upstream: "http://127.0.0.1:8888/searx/", host: "{removed}"

This leads me to believe it's an issue directly related to uwsgi.

For now I will use a work-around by putting the process into tmux, however I would like to figure out why uwsgi is failing.

@dalf dalf added the bug label Aug 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.