Nginx 配置 502 bad gateway 错误

Question

我有一个配置好的 nginx 站点在我运行时启用/可用：

nginx -t

我通过了成功的测试，当我：

service nginx restart
thin restart -s 1

我的 502 错误消失了，但仅持续了 10 秒钟，然后又出现了。我的可用网站是：

upstream myapp {
server 0.0.0.0:3000;

}

服务器{ 听 80 默认；

access_log /webservices/crawler/log/access.log;
error_log /webservices/crawler/error.log;

root   /webservices/crawler/public/;
index  index.html;

client_max_body_size 500M;

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;

    if (-f $request_filename/index.html) {
        rewrite (.*) $1/index.html;
        break;
    }

    if (-f $request_filename.html) {
        rewrite (.*) $1.html;
        break;
    }

    if (!-f $request_filename) {
        proxy_pass http://myapp;
        break;
    }
}

}

有人知道为什么我的配置只能运行几秒钟吗？感谢您的帮助，如果您需要查看我的任何其他代码，请告诉我。

thin restart -s 2 输出：

    /# thin restart -s 2
Stopping server on 0.0.0.0:3000 ... 
/usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:131:in `send_signal': Can't stop process, no PID found in tmp/pids/thin.3000.pid (Thin::PidFileNotFound)
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:113:in `kill'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:93:in `block in stop'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:134:in `tail_log'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:92:in `stop'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:187:in `run_command'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:152:in `run!'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/bin/thin:6:in `<top (required)>'
    from /usr/local/bin/thin:23:in `load'
    from /usr/local/bin/thin:23:in `<main>'
Stopping server on 0.0.0.0:3001 ... 
/usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:131:in `send_signal': Can't stop process, no PID found in tmp/pids/thin.3001.pid (Thin::PidFileNotFound)
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:113:in `kill'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:93:in `block in stop'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:134:in `tail_log'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:92:in `stop'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:187:in `run_command'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:152:in `run!'
    from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/bin/thin:6:in `<top (required)>'
    from /usr/local/bin/thin:23:in `load'
    from /usr/local/bin/thin:23:in `<main>'
Starting server on 0.0.0.0:3000 ... 
Starting server on 0.0.0.0:3001 ... 

我很确定这是一个瘦问题，而不是 nginx 问题，所以我发布了一个更新。如有任何混淆，请见谅。

我的网站启动了大约 10 秒，然后我收到 502 nginx 错误。我的 nginx 配置似乎很好，并且 nginx -t 成功。我的错误信息是这样的：

瘦重启-s 5

/usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:131:in send_signal': Can't stop process, no PID found in tmp/pids/thin.3004.pid (Thin::PidFileNotFound) from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/daemonizing.rb:113:inkill' 来自 /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:93:in block in stop' from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:134:intail_log' 来自 /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/controllers/controller.rb:92:in stop' from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:187:inrun_command' 来自 /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/lib/thin/runner.rb:152:in run!' from /usr/local/lib/ruby/gems/2.0.0/gems/thin-1.5.1/bin/thin:6:in' 来自 /usr/local/bin/thin:23:in load' from /usr/local/bin/thin:23:in'

我已经检查了 PID，它们在那里。有谁知道这里发生了什么？谢谢你，我很感激任何建议。

Answer 1

我找到了我需要运行的东西来清理那些细小的错误。我不知道为什么但正在运行：

bundle exec thin start -p 3000

解决了我的问题。感谢大家的帮助！没有你，我找不到它。