【发布时间】：2021-05-21 02:33:18
【问题描述】：
我正在使用 Linode 部署 Rails 应用程序。我一直在关注这个教程：https://matthewhoelter.com/2020/11/10/deploying-ruby-on-rails-for-ubuntu-2004.html
当我尝试访问我的网站时，我收到 ERR_CONNECTION_REFUSED。
我在调试时遇到了麻烦。
nginx.conf
upstream puma {
server unix:///home/deploy/apps/PhotographerFind/shared/tmp/sockets/PhotographerFind-puma.sock;
}
server {
listen 80 default_server deferred;
# If you're planning on using SSL (which you should), you can also go ahead and fill out the following server_name variable:
# server_name example.com;
# Don't forget to update these, too
root /home/deploy/apps/PhotographerFind/current/public;
access_log /home/deploy/apps/PhotographerFind/current/log/nginx.access.log;
error_log /home/deploy/apps/PhotographerFind/current/log/nginx.error.log info;
location ^~ /assets/ {
gzip_static on;
expires max;
add_header Cache-Control public;
}
try_files $uri/index.html $uri @puma;
location @puma {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass http://puma;
}
error_page 500 502 503 504 /500.html;
client_max_body_size 10M;
keepalive_timeout 10;
}
deploy.rb
# # config valid for current version and patch releases of Capistrano
# lock "~> 3.15.0"
# Change these
server 'ip.address.here', port: 22, roles: [:web, :app, :db], primary: true
set :repo_url, 'git@ssh.dev.azure.com:v3/gitrepo/myrepo/myrepo'
set :application, 'PhotographerFind'
# If using Digital Ocean's Ruby on Rails Marketplace framework, your username is 'rails'
set :user, 'deploy'
set :puma_threads, [4, 16]
set :puma_workers, 0
# Don't change these unless you know what you're doing
set :pty, true
set :use_sudo, false
set :stage, :production
set :deploy_via, :remote_cache
set :deploy_to, "/home/#{fetch(:user)}/apps/#{fetch(:application)}"
set :puma_bind, "unix://#{shared_path}/tmp/sockets/#{fetch(:application)}-puma.sock"
set :puma_state, "#{shared_path}/tmp/pids/puma.state"
set :puma_pid, "#{shared_path}/tmp/pids/puma.pid"
set :puma_access_log, "#{release_path}/log/puma.access.log"
set :puma_error_log, "#{release_path}/log/puma.error.log"
set :ssh_options, { forward_agent: true, user: fetch(:user), keys: %w(~/.ssh/id_rsa.pub) }
set :puma_preload_app, true
set :puma_worker_timeout, nil
set :puma_init_active_record, true # Change to false when not using ActiveRecord
namespace :puma do
desc 'Create Directories for Puma Pids and Socket'
task :make_dirs do
on roles(:app) do
execute "mkdir #{shared_path}/tmp/sockets -p"
execute "mkdir #{shared_path}/tmp/pids -p"
end
end
before :start, :make_dirs
end
namespace :deploy do
desc "Make sure local git is in sync with remote."
task :check_revision do
on roles(:app) do
unless `git rev-parse HEAD` == `git rev-parse origin/master`
puts "WARNING: HEAD is not the same as origin/master"
puts "Run `git push` to sync changes."
exit
end
end
end
desc 'Initial Deploy'
task :initial do
on roles(:app) do
before 'deploy:restart', 'puma:start'
invoke 'deploy'
end
end
desc 'Restart application'
task :restart do
on roles(:app), in: :sequence, wait: 5 do
invoke 'puma:restart'
end
end
before :starting, :check_revision
after :finishing, :compile_assets
after :finishing, :cleanup
end
set :linked_files, fetch(:linked_files, []).push("config/master.key")
puma.access.log
Puma starting in single mode...
* Version 3.12.6 (ruby 2.6.3-p62), codename: Llamas in Pajamas
* Min threads: 4, max threads: 16
* Environment: production
* Daemonizing...
=== puma startup: 2021-02-18 06:23:44 +0000 ===
=== puma startup: 2021-02-18 06:26:53 +0000 ===
* Listening on unix:///home/deploy/apps/PhotographerFind/shared/tmp/sockets/PhotographerFind-puma.sock
puma.error.log
=== puma startup: 2021-02-18 06:23:44 +0000 ===
/home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/binder.rb:395:in `for_fd': Bad file descriptor - fstat(2) (Errno::EBADF)
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/binder.rb:395:in `inherit_unix_listener'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/binder.rb:115:in `block in parse'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/binder.rb:90:in `each'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/binder.rb:90:in `parse'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/runner.rb:153:in `load_and_bind'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/single.rb:98:in `run'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/launcher.rb:186:in `run'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/lib/puma/cli.rb:80:in `run'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/gems/puma-3.12.6/bin/puma:10:in `<top (required)>'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/bin/puma:23:in `load'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/bin/puma:23:in `<main>'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/bin/ruby_executable_hooks:24:in `eval'
from /home/deploy/apps/PhotographerFind/shared/bundle/ruby/2.6.0/bin/ruby_executable_hooks:24:in `<main>'
=== puma startup: 2021-02-18 06:26:53 +0000 ===
我认为这可能指向问题，但似乎不是每次 puma 启动时都会出现，所以我不太确定这里发生了什么。
更新
我认为可能与端口有关，但这是sudo netstat -ntlp | grep LISTEN的输出
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 7307/nginx: master
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 963/sshd
tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 955/postgres
tcp6 0 0 127.0.0.1:9200 :::* LISTEN 3892/java
tcp6 0 0 ::1:9200 :::* LISTEN 3892/java
tcp6 0 0 127.0.0.1:9300 :::* LISTEN 3892/java
tcp6 0 0 ::1:9300 :::* LISTEN 3892/java
tcp6 0 0 :::22 :::* LISTEN 963/sshd
tcp6 0 0 :::5432 :::* LISTEN 955/postgres
这是/var/log/nginx/error.log中的内容：
2021/02/18 23:09:58 [notice] 7325#7325: signal process started
我注意到 Puma 仅在重新启动时抛出错误文件描述符。它似乎正在运行。这是puma.access.log的内容：
=== puma startup: 2021-02-18 23:04:28 +0000 ===
[6971] - Worker 0 (pid: 6973) booted, phase: 0
[6971] - Worker 1 (pid: 6979) booted, phase: 0
我认为这可能是端口问题，并从sudo ufw status numbered 获取此输出，这似乎是正确的：
Status: active
To Action From
-- ------ ----
[ 1] 80,443/tcp ALLOW IN Anywhere
[ 2] 22,80,443/tcp ALLOW IN Anywhere
[ 3] 80,443/tcp (v6) ALLOW IN Anywhere (v6)
[ 4] 22,80,443/tcp (v6) ALLOW IN Anywhere (v6)
在这一点上，我不知道在哪里寻找根本问题。有什么建议吗？
编辑 #2 我现在注意到，如果我尝试访问浏览器中的 IP 地址，我会收到 Connection Refused，但如果我尝试访问 IPADDRESS:3000，我会收到 Connection Timed Out。我不确定这是否相关。
【问题讨论】：
-
这并不能真正回答您的问题，但我遵循了 Linode 上的 Ruby Yagi 部署教程，几乎没有问题。虽然仔细观察，但我发现您使用的是 Puma，而本教程使用的是 Passenger……rubyyagi.com/rails-deploy-automate-ansible
-
@Matthew 你需要做任何防火墙配置吗？
-
不，我自己不需要对防火墙做任何事情（我认为 Ansible 脚本也没有 - github.com/cupnoodle/rails-ansible）。关于你的编辑，你不应该去 IPADDRESS:3000，那只是为了开发......生产中（可能）没有监听端口 3000，因此为什么你会超时
-
@Matthew 是的，我用它来测试只是为了看看我是否能得到任何东西。
RAILS_ENV=production rails server --binding=server_public_IP
标签： ruby-on-rails nginx capistrano linode