“Erro 768 worker_connections não é suficiente” após uma nova instalação do nginx e do ROR

2

Eu tenho uma nova instalação de nginx e ruby on rails. Mas isso me dá um '500 Internal Server Error' durante o teste.

O error.log do meu aplicativo tem o seguinte:

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"

O nginx.conf tem o seguinte:

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;
}

arquivo de configuração 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;
  }
}

Depois de voltar a usar ip 127.0.0.1:3000 e 127.0.0.1:3001 dentro do bloco upstream, o servidor gerou os erros:

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"

Atualização 05/05/2014: Eu corri o seguinte comando para verificar a conexão:

telnet 127.0.0.1 3000 

e o resultado foi:

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

Eu tentei reiniciar o servidor thin, mas recebi mensagens de erro.

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

Erro:

/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'
    
por Purres 02.05.2014 / 02:58

2 respostas

3

As diretivas proxy_set_header e proxy_redirect devem estar em location @ruby block.

Para o bloco upstream , você deve usar localhost e a porta real do seu servidor Ruby. Sem porta, o upstream se conectaria a essa instância do servidor nginx, que é um loop.

    
por 03.05.2014 / 07:47
1

Pergunta antiga, mas eu tive o mesmo problema e a resposta aceita não funcionou para mim.

Eu tive que aumentar o número de worker_connections , conforme declarado aqui .

/etc/nginx/nginx.conf

events {
    worker_connections 20000;
}
    
por 08.04.2016 / 15:03