由 nginx uwsgi 提供服务的 flask 应用程序返回 502

由 nginx uwsgi 提供服务的 flask 应用程序返回 502

我无法连接到由 nginx 和 uwsgi 提供的 flask 应用程序(searx 搜索引擎)。

我的 Web 服务器显示“502 Bad Gateway nginx”

这是我的 nginx 错误:错误日志:/var/log/nginx/error.log

[crit] 2688#2688: *4 connect() to unix:/run/uwsgi/app/searx/socket.sock failed 
(2: No such file or directory) while connecting to upstream,
client: 216.186.XXX.XXX, server searx.mysite.com, 
request: "GET / HTTP/1.1", 
upstream: "uwsgi://unix:/run/uwsgi/app/searx/socket.sock:", 
host: "searx.mysite.com"

所以我可以看到socket.sock与上游不一样。

这是我的 nginx.conf

user http;
worker_processes auto;
worker_cpu_affinity auto;

events {
    multi_accept on;
    worker_connections 1024;
}

http {
    charset utf-8;
    sendfile on;
    tcp-nopush on;
    tcp_nodelay on;
    server_tokens off;
    log_not_found off;
    types_hash_max_size 4096;
    client_max_body_size 16M;

    include mime.types;
    default_type application/octet-stream;

    keepalive_timeout 65;

    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log warn;

    include /etc/nginx/sites-enabled/*;
}

这是我的 searx.conf,也是我指定 .sock 文件位置的唯一地方:

/etc/nginx/sites-enabled/searx.conf

server {
    listen 80;
    server_name searx.mysite.com;
    
    location / {
        include uwsgi_params;
        uwsgi_pass unix:/run/uwsgi/app/searx/socket.sock;
    }
    
    root /usr/local/searx/searx-src/searx;
    location /static { }
}

当我查看我的套接字文件夹时,那里没有文件......

ls -alh /run/uwsgi/app/searx/
total 0
drwxr-xr-x 2 searx searx 40 Jul 22 05:02 .
drwxr-xr-x 3 root  root  60 Jul 22 05:02 ..

我用来运行 uwsgi 的命令是:

exec chpst -u http env LC_ALL=en_US.UTF-8 /usr/bin/uwsgi --master --die-on-term --emperor /etc/uwsgi/sites

我用来运行 nginx 的命令:

exec chpst -u root /usr/bin/nginx -c /etc/nginx/nginx.conf -g "daemon off;"

这是我的 searx uwsgi 文件

/etc/uwsgi/sites/searx.ini

[uwsgi]
project = searx
uid = searx
gid = searx
base = /usr/local/searx/searx-src

chdir = %(base)/%(project)
env = SEARX_SETTINGS_PATH=/etc/searx/settings.yml

disable-logging = false
workers = 2

chmod-socket = 666
vacuum = true

single-interpreter = true
master = true
plugin = python
lazy-apps = true
enable-threads = true

module = searx.webapp

route-run = fixpathinfo:

virtualenv = /usr/local/searx/searx-pyenv
pythonpath = %(base)

# NOTE: if I add or delete the next line there is no difference in output
socket = /run/uwsgi/app/searx/socket.sock

进一步挖掘:在 searx.ini 中我设置disable-logging = false并在/var/log/uwsgi/current日志中发现了这一点:

thunder lock: disabled (you can enable it with --thunder-lock
bind(): Permission denied [core/socket.c line 230]
Wed July 22 15:05:31 2020 - [emperor] curse the uwsgi instance searx.ini (pid: 3320)
Wed July 22 15:05:31 2020 - [emperor] removed uwsgi instance searx.ini

那么我的 searx.ini 或者我调用它的方式肯定有问题?

我不确定你还需要什么其他信息,但我很乐意根据需要更新问题。我已经研究这个问题好几天了,所以如果你能提供任何帮助,我将不胜感激。

答案1

找到问题了。为谷歌后人解答...

当然是文件权限:

  1. 我将用户 searx 添加到组 http: usermod -a -G http searx
  2. 我把 searx 目录改为以 http 作为它的组:chgrp -R http /usr/local/searx
  3. 我把 searx 目录设为可由组写入: chmod -R g+w user/local/searx
  4. 对我的 socket.sock 文件夹执行了同样操作: chgrp -R http /run/uwsgi/app/searx
  5. 并使该文件夹可由组写入:chmod -R g+w /run/uwsgi/app/searx
  6. 重新启动 nginx 和 uwsgi。

相关内容