Question

我们在AWS EC2 M4.xlarge实例中运行我们的服务器，我们看到了websocket连接的无法解释的行为。
问题： 我们的客户端（运行python websocket-client连接）连接到nginx后面的tornado websocket服务器， ALL 被丢弃在连接一段时间（3-6小时）后ping / pong timedout的同一时间和原因相同。不确定我们是否错误地设置了一些配置。

以下是我们的sysctl.conf的配置：

net.core.somaxconn = 65536 net.ipv4.tcp_max_tw_buckets = 1440000 net.ipv4.tcp_fin_timeout = 15
/etc/nginx/nginx.conf：

user www-data;
worker_processes auto;
pid /run/nginx.pid;
events {
    worker_connections 65000;
    multi_accept on;
}
http {
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 15;
    keepalive_requests 100000;
    types_hash_max_size 2048;   
    include /etc/nginx/mime.types;
    default_type application/octet-stream;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
    ssl_prefer_server_ciphers on;
    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;
    gzip on;
    gzip_disable "msie6";
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

这是我们对应用程序服务器的配置。

upstream ourserver {
    server 127.0.0.1:9999;
}
server {
    listen  80;
    listen [::]:80 ipv6only=on;
    return 301 https://$host$request_uri;
}
server {
    listen 443 default_server;
    listen [::]:443 default_server ipv6only=on;
    server_name **DNS**;
    ssl on;
    ssl_protocols    SSLv3 TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers    HIGH:!aNULL:!MD5;
    ssl_certificate /etc/ssl/certs/ssl-bundle.crt;
    ssl_certificate_key /etc/ssl/private/my.key;
    client_max_body_size 10m;
    client_body_buffer_size 128k;
    client_header_buffer_size 1k;
    keepalive_timeout 15s;
    add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;";
    location /secure/ {
        proxy_pass http://ourserver;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_read_timeout 86400;
    }
    location / {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_pass http://ourserver;
        proxy_read_timeout 120s;
        proxy_connect_timeout 120s;
    }
}

非常感谢任何帮助。

Answer 1

由于数据库调用，我的on_message有一个阻塞呼叫，需要20到200毫秒。此延迟传播到进入的其余事件，最终导致客户端丢弃套接字。

Nginx背后的龙卷风为websockets - 超时

1 个答案: