☰

全新安装 nginx 和 ROR 后出现“768 worker_connections 不足”错误

tag-icon • tag-icon ubuntu nginx ruby-on-rails thin
全新安装 nginx 和 ROR 后出现“768 worker_connections 不足”错误

我全新安装了 nginx 和 ruby​​ on rails。但在测试时它给出了“500 内部服务器错误”。

我的应用程序的 error.log 包含以下内容：

2014/05/01 17:27:15 [alert] 1423#0: *6892 768 worker_connections are not enough while connecting to upstream, client: 24.15.27.113, server: example.com, request: "GET / HTTP/1.0", upstream: "http://24.15.27.113:80/", host: "myapp"
2014/05/01 17:27:16 [alert] 1423#0: *7656 768 worker_connections are not enough while connecting to upstream, client: 24.15.27.113, server: example.com, request: "GET /favicon.ico HTTP/1.0", upstream: "http://24.15.27.113:80/favicon.ico", host: "myapp"
2014/05/01 17:45:50 [alert] 1453#0: *766 768 worker_connections are not enough while connecting to upstream, client: 24.15.27.113, server: example.com, request: "GET / HTTP/1.0", upstream: "http://24.15.27.113:80/", host: "myapp"
2014/05/01 17:45:50 [alert] 1453#0: *1530 768 worker_connections are not enough while connecting to upstream, client: 24.15.27.113, server: example.com, request: "GET /favicon.ico HTTP/1.0", upstream: "http://24.15.27.113:80/favicon.ico", host: "myapp"

nginx.conf 包含以下内容：

user www-data;
worker_processes 4;
pid /var/run/nginx.pid;

events {
    worker_connections 768;
}

http {

    ##
    # Basic Settings
    ##

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;

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

    ##
    # Logging Settings
    ##

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

    ##
    # Gzip Settings
    ##

    gzip on;
    gzip_disable "msie6";

    ##
    # Virtual Host Configs
    ##

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;

    fastcgi_buffers 8 16k;
    fastcgi_buffer_size 32k;
}

myapp.example.com 配置文件：

upstream myapp {
  #server 24.15.27.113;
  #server 24.15.27.113:3001;
  #server 24.15.27.113:3002;
  server 127.0.0.1:3000;
  server 127.0.0.1:3001;
  #server 127.0.0.1:3002;
}
server {
  listen   80;
  server_name .example.com;

  access_log /var/www/myapp.example.com/log/access.log;
  error_log  /var/www/myapp.example.com/log/error.log;
  root     /var/www/myapp.example.com;
  index    index.html;

  location / {
    proxy_set_header  X-Real-IP  $remote_addr;
    proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header  Host $http_host;
    proxy_redirect  off;
    try_files /system/maintenance.html $uri $uri/index.html $uri.html @ruby;
  }

  location @ruby {
    proxy_pass http://myapp;
  }
}

切换回使用上游块内的 ip 127.0.0.1:3000 和 127.0.0.1:3001 后，服务器生成了以下错误：

2014/05/05 10:34:39 [error] 6158#0: *2 no live upstreams while connecting to upstream, client: 52.74.130.210, server: example.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:3001”, host: "24.15.27.113"

2014/05/05 10:34:39 [error] 6158#0: *2 no live upstreams while connecting to upstream, client: 52.74.130.210, server: example.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "24.15.27.113"

2014/05/05 10:34:39 [error] 6158#0: *2 no live upstreams while connecting to upstream, client: 52.74.130.210, server: example.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://myapp/favicon.ico", host: "24.15.27.113"

更新日期：2014 年 5 月 5 日：我运行以下命令来检查连接：

telnet 127.0.0.1 3000

结果是：

Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

我尝试重新启动瘦服务器，但收到错误消息。

thin restart -C /etc/thin/myapp.example.com -o 3000

错误：

/usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.2/lib/thin/daemonizing.rb:129:in `send_signal': Can't stop process, no PID found in tmp/pids/thin.3000.pid (Thin::PidFileNotFound)
from /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.2/lib/thin/daemonizing.rb:111:in `kill'
from /usr/local/rvm/gems/ruby-2.1.1/gems/thin-1.6.2/lib/thin/controllers/controller.rb:94:in `block in stop'

答案1

和proxy_set_header指令proxy_redirect应该在location @ruby块中。

对于upstreamblock，您应该使用localhostRuby 服务器的实际端口。如果没有端口，上游将连接到此 nginx 服务器实例，这是一个循环。

答案2

老问题，但我遇到了同样的问题并且接受的答案对我没有用。

我不得不增加worker_connections， 就像声明的那样这里。

/etc/nginx/nginx.conf

events {
    worker_connections 20000;
}

相关内容