NGINX + uWSGI连接由Peer重置

Question

我正在尝试使用uWSGI在NGINX上托管Bottle Application。

这是我的nginx.conf

location /myapp/ {
        include uwsgi_params;
        uwsgi_param X-Real-IP $remote_addr;
        uwsgi_param Host $http_host;
        uwsgi_param UWSGI_SCRIPT myapp;
        uwsgi_pass 127.0.0.1:8080;
    }

我正在运行uwsgi

uwsgi --enable-threads --socket :8080 --plugin python -- wsgi-file ./myApp/myapp.py

我正在使用POST请求。对于使用dev Http Client的那个。当我发送请求时，这是无限的

http://localhost/myapp

uWSGI服务器接收请求并打印

[pid: 4683|app: 0|req: 1/1] 127.0.0.1 () {50 vars in 806 bytes} [Thu Oct 25 12:29:36 2012] POST /myapp => generated 737 bytes in 11 msecs (HTTP/1.1 404) 2 headers in 87 bytes (1 switches on core 0)

但在nginx错误日志中

2012/10/25 12:20:16 [error] 4364#0: *11 readv() failed (104: Connection reset by peer) while reading upstream, client: 127.0.0.1, server: localhost, request: "POST /myApp/myapp/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:8080", host: "localhost"

该怎么办？

Answer 1

确保在您的应用程序中使用您的帖子数据

例如，如果你有一个Django / python应用程序

def my_view(request):

    # ensure to read the post data, even if you don't need it
    # without this you get a: failed (104: Connection reset by peer)
    data = request.DATA

    return HttpResponse("Hello World")

一些细节：https://uwsgi-docs.readthedocs.io/en/latest/ThingsToKnow.html

Answer 2

如果不在应用程序中读取数据，则无法从客户端发布数据。虽然这在uWSGI中不是问题，但nginx会失败。您可以使用uWSGI的--post-buffering选项“伪造”该东西，以自动从套接字读取数据（如果可用），但您最好“修复”（即使我不认为这是一个错误）应用

Answer 3

当请求的主体没有被消耗时会发生此问题，因为uwsgi无法知道在某些时候是否仍然需要它。所以uwsgi将继续保持数据，直到它被消耗或直到nginx重置连接（因为上游超时）。

uwsgi的作者解释它here：

08:21 < unbit> plaes: does your DELETE request (not-response) have a body ?
08:40 < unbit> and do you read that body in your app ?
08:41 < unbit> from the nginx logs it looks like it has a body and you are not reading it in the app
08:43 < plaes> so DELETE request shouldn't have the body?
08:43 < unbit> no i mean if a request has a body you have to read/consume it
08:44 < unbit> otherwise the socket will be clobbered

因此，要解决此问题，您需要确保始终读取整个请求正文，如果不需要，则发送正文（例如，对于DELETE）。

Answer 4

不使用线程！

我在uwsgi下使用Python中的Global Interpretator Lock也遇到了同样的问题。当我不使用线程 - 不连接重置。

uwsgi配置示例（服务器上的1Gb Ram）

[root@mail uwsgi]# cat myproj_config.yaml 
uwsgi:
    print: Myproject Configuration Started
    socket: /var/tmp/myproject_uwsgi.sock
    pythonpath: /sites/myproject/myproj
    env: DJANGO_SETTINGS_MODULE=settings
    module: wsgi
    chdir: /sites/myproject/myproj
    daemonize: /sites/myproject/log/uwsgi.log
    max-requests: 4000
    buffer-size: 32768
    harakiri: 30
    harakiri-verbose: true
    reload-mercy: 8
    vacuum: true
    master: 1
    post-buffering: 8192
    processes: 4
    no-orphans: 1
    touch-reload: /sites/myproject/log/uwsgi
    post-buffering: 8192