登录
当前位置： 首页 > 知识库问答 >
问题：

在Heroku的puma上部署rails应用程序时出错

阎嘉荣
2023-03-14

我正在尝试部署一个运行在puma和jruby上的rails应用程序。程序文件如下所示

web: bundle exec puma -C config/puma.rb -p $PORT -e $RACK_ENV

彪马的配置放在

配置/puma.rb

if ENV['RACK_ENV'] != 'production' || ENV['RAILS_ENV'] != 'production'
  workers Integer(ENV['PUMA_WORKERS'] || 4)
end

threads Integer(ENV['MIN_THREADS']  || 1), Integer(ENV['MAX_THREADS'] || 4)

rackup      DefaultRackup
port ENV['PORT'] || 3000
environment ENV['RACK_ENV'] || 'development'
preload_app!

on_worker_boot do
  # worker specific setup
  ActiveSupport.on_load(:active_record) do
    config = ActiveRecord::Base.configurations[Rails.env] ||
                Rails.application.config.database_configuration[Rails.env]
    config['pool'] = ENV['MAX_THREADS'] || 16
    ActiveRecord::Base.establish_connection(config)
  end
end

我对工人有条件初始化的原因是因为Heroku抱怨（或者可能是彪马）工人模式不适用于JRuby和Windows；无论如何，

我在heroku上注意到的奇怪行为是（与我的本地环境不同），集群Puma实例启动时没有任何问题，并选择两个不同的端口来绑定，即3000和5000。

但是，在生产过程中，即Heroku，这会导致崩溃

2014-06-23T08:50:54.545724+00:00 heroku[web.1]: State changed from crashed to starting
2014-06-23T08:51:02.510184+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Djava.rmi.server.useCodebaseOnly=true
2014-06-23T08:51:01.333763+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb -p 49576 -e production`
2014-06-23T08:51:21.658663+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Djava.rmi.server.useCodebaseOnly=true
2014-06-23T08:51:44.964380+00:00 app[web.1]: * Version 2.8.2 (jruby 1.9.3), codename: Sir Edmund Percival Hillary
2014-06-23T08:51:44.962724+00:00 app[web.1]: The signal USR1 is in use by the JVM and will not work correctly on this platform
2014-06-23T08:51:44.964563+00:00 app[web.1]: * Min threads: 1, max threads: 4
2014-06-23T08:51:44.964738+00:00 app[web.1]: * Environment: production
2014-06-23T08:51:44.963925+00:00 app[web.1]: Puma starting in single mode...
2014-06-23T08:51:57.852471+00:00 app[web.1]: Errno::EADDRINUSE: Address already in use - bind - Address already in use
2014-06-23T08:51:57.830580+00:00 app[web.1]: * Listening on tcp://0.0.0.0:49576
2014-06-23T08:51:57.852474+00:00 app[web.1]:         initialize at org/jruby/ext/socket/RubyTCPServer.java:118
2014-06-23T08:51:57.852478+00:00 app[web.1]:   add_tcp_listener at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/binder.rb:195
2014-06-23T08:51:57.852476+00:00 app[web.1]:                new at org/jruby/RubyIO.java:852
2014-06-23T08:51:57.850256+00:00 app[web.1]: * Listening on tcp://0.0.0.0:49576
2014-06-23T08:51:57.852479+00:00 app[web.1]:              parse at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/binder.rb:96
2014-06-23T08:51:57.852481+00:00 app[web.1]:               each at org/jruby/RubyArray.java:1613
2014-06-23T08:51:57.852482+00:00 app[web.1]:              parse at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/binder.rb:82
2014-06-23T08:51:57.852484+00:00 app[web.1]:      load_and_bind at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/runner.rb:119
2014-06-23T08:51:57.852486+00:00 app[web.1]:                run at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/single.rb:73
2014-06-23T08:51:57.852487+00:00 app[web.1]:                run at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/lib/puma/cli.rb:499
2014-06-23T08:51:57.852489+00:00 app[web.1]:             (root) at /app/vendor/bundle/jruby/1.9/gems/puma-2.8.2-java/bin/puma:10
2014-06-23T08:51:57.852491+00:00 app[web.1]:               load at org/jruby/RubyKernel.java:1099
2014-06-23T08:51:57.852492+00:00 app[web.1]:             (root) at /app/vendor/bundle/jruby/1.9/bin/puma:23
2014-06-23T08:51:59.347012+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-23T08:51:59.333790+00:00 heroku[web.1]: Process exited with status 1

这种奇怪的启动行为在我的笔记本电脑上运行时是看不到的。

我让puma在Heroku中使用jruby的唯一方法就是通过这个设置

if ENV['RACK_ENV'] != 'production' || ENV['RAILS_ENV'] != 'production'
  workers Integer(ENV['PUMA_WORKERS'] || 4)
  port ENV['PORT'] || 3000
  environment ENV['RACK_ENV'] || 'development'
end

threads Integer(ENV['MIN_THREADS']  || 1), Integer(ENV['MAX_THREADS'] || 4)

rackup      DefaultRackup
preload_app!

on_worker_boot do
  # worker specific setup
  ActiveSupport.on_load(:active_record) do
    config = ActiveRecord::Base.configurations[Rails.env] ||
                Rails.application.config.database_configuration[Rails.env]
    config['pool'] = ENV['MAX_THREADS'] || 16
    ActiveRecord::Base.establish_connection(config)
  end
end

也就是说，如果端口和环境指令在外面，if块Heroku试图在同一个端口上运行两个实例，这显然会导致崩溃。

*更新*

程序文件

web: bundle exec puma -C config/puma.rb

配置/puma.rb

if ENV['RACK_ENV'] != 'production' || ENV['RAILS_ENV'] != 'production'
  workers Integer(ENV['PUMA_WORKERS'] || 4)
end

threads Integer(ENV['MIN_THREADS']  || 1), Integer(ENV['MAX_THREADS'] || 16)

rackup      DefaultRackup
port ENV['PORT'] || 3000
environment ENV['RACK_ENV'] || 'development'
preload_app!

on_worker_boot do
  # worker specific setup
  ActiveSupport.on_load(:active_record) do
    config = ActiveRecord::Base.configurations[Rails.env] ||
                Rails.application.config.database_configuration[Rails.env]
    config['pool'] = ENV['MAX_THREADS'] || 16
    ActiveRecord::Base.establish_connection(config)
  end
end

条件块的原因（引自初始问题描述

我有条件初始化工人的原因是因为Heroku抱怨（或者可能是彪马）工人模式不适用于JRuby和Windows；

和错误日志（即使我删除了JRUBY，条件工作块）并尝试在集群模式下运行

606 2014-06-23T07:13:42.058507+00:00 heroku[api]: Release v35 created by foo@bar.com
 607 2014-06-23T07:13:47.674708+00:00 app[web.1]: [2] Puma starting in cluster mode...
 608 2014-06-23T07:13:47.674777+00:00 app[web.1]: [2] * Version 2.8.2 (ruby 2.1.1-p76), codename: Sir Edmund Percival Hillary
 609 2014-06-23T07:13:47.674816+00:00 app[web.1]: [2] * Min threads: 1, max threads: 16
 610 2014-06-23T07:13:47.674939+00:00 app[web.1]: [2] * Preloading application
 611 2014-06-23T07:13:47.674858+00:00 app[web.1]: [2] * Environment: production
 612 2014-06-23T07:13:47.674900+00:00 app[web.1]: [2] * Process workers: 4
 613 2014-06-23T07:13:49.078330+00:00 app[web.1]: [2] * Listening on tcp://0.0.0.0:45245
 614 2014-06-23T07:13:49.078766+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `initialize': Address already in use - bind(2) for "0.0.0.0     " port 45245 (Errno::EADDRINUSE)
 615 2014-06-23T07:13:49.078775+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `add_tcp_listener'
 616 2014-06-23T07:13:49.078771+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `new'
 617 2014-06-23T07:13:49.078780+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:82:in `each'
 618 2014-06-23T07:13:49.078785+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/runner.rb:119:in `load_and_bind'
 619 2014-06-23T07:13:49.078778+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:96:in `block in parse'
 620 2014-06-23T07:13:49.078784+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:82:in `parse'
 621 2014-06-23T07:13:49.078793+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/cli.rb:499:in `run'
 622 2014-06-23T07:13:49.078789+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/cluster.rb:271:in `run'
 623 2014-06-23T07:13:49.078794+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/bin/puma:10:in `<top (required)>'
 624 2014-06-23T07:13:49.078798+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/bin/puma:23:in `load'
 625 2014-06-23T07:13:49.078801+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/bin/puma:23:in `<main>'
 626 2014-06-23T07:13:49.078565+00:00 app[web.1]: [2] * Listening on tcp://0.0.0.0:45245
 627 2014-06-23T07:13:50.359244+00:00 heroku[web.1]: Process exited with status 1
 628 2014-06-23T07:13:45.838792+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb -p 45245 -e production`
 629 2014-06-23T07:13:50.385427+00:00 heroku[web.1]: State changed from starting to crashed
 630 2014-06-23T07:13:50.385913+00:00 heroku[web.1]: State changed from crashed to starting
 631 2014-06-23T07:13:57.445391+00:00 app[web.1]: [2] Puma starting in cluster mode...
 632 2014-06-23T07:13:57.445417+00:00 app[web.1]: [2] * Environment: production
 633 2014-06-23T07:13:57.445413+00:00 app[web.1]: [2] * Version 2.8.2 (ruby 2.1.1-p76), codename: Sir Edmund Percival Hillary
 634 2014-06-23T07:13:57.445415+00:00 app[web.1]: [2] * Min threads: 1, max threads: 16
 635 2014-06-23T07:13:57.445419+00:00 app[web.1]: [2] * Process workers: 4
 636 2014-06-23T07:13:57.445423+00:00 app[web.1]: [2] * Preloading application
 637 2014-06-23T07:13:54.371058+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb -p 33243 -e production`
 638 2014-06-23T07:13:59.883490+00:00 app[web.1]: /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `initialize': Address already in use - bind(2) for "0.0.0.0     " port 33243 (Errno::EADDRINUSE)
 639 2014-06-23T07:13:59.882892+00:00 app[web.1]: [2] * Listening on tcp://0.0.0.0:33243
 640 2014-06-23T07:13:59.883501+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:96:in `block in parse'
 641 2014-06-23T07:13:59.883494+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `new'
 642 2014-06-23T07:13:59.883499+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:195:in `add_tcp_listener'
 643 2014-06-23T07:13:59.883506+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:82:in `parse'
 644 2014-06-23T07:13:59.883510+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/runner.rb:119:in `load_and_bind'
 645 2014-06-23T07:13:59.883503+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/binder.rb:82:in `each'
 646 2014-06-23T07:13:59.883512+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/cluster.rb:271:in `run'
 647 2014-06-23T07:13:59.883519+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/bin/puma:23:in `load'
 648 2014-06-23T07:13:59.883517+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/bin/puma:10:in `<top (required)>'
 649 2014-06-23T07:13:59.883514+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/gems/puma-2.8.2/lib/puma/cli.rb:499:in `run'
 650 2014-06-23T07:13:59.883525+00:00 app[web.1]:  from /app/vendor/bundle/ruby/2.1.0/bin/puma:23:in `<main>'
 651 2014-06-23T07:13:59.883273+00:00 app[web.1]: [2] * Listening on tcp://0.0.0.0:33243
 652 2014-06-23T07:14:01.451472+00:00 heroku[api]: Set DEV-2-PASS config vars by foo@bar.com
 653 2014-06-23T07:14:01.451540+00:00 heroku[api]: Release v36 created by foo@bar.com
 654 2014-06-23T07:14:01.624035+00:00 heroku[web.1]: State changed from starting to crashed
 655 2014-06-23T07:14:01.963688+00:00 heroku[web.1]: State changed from crashed to starting
 656 2014-06-23T07:14:01.615855+00:00 heroku[web.1]: Process exited with status 1

共有1个答案

冯通
2023-03-14

我和你有同样的问题。

它似乎与端口的重复定义有关

首先在Procfile中，然后在config/puma.rb文件中

我从Procfile（以及环境）中删除了端口，因为这已经在config/puma.rb中定义。

web: bundle exec puma -C config/puma.rb
 类似资料：
  • 将Rails应用程序部署到Heroku时出错

    我正在尝试将我的应用程序部署到Heroku，但似乎存在一些问题。每次我尝试： 我的heroku日志告诉我，我的应用程序崩溃了，我错过了“调试器”宝石。我在Heroku上找到了这条线索和这一页。当我尝试安装“byebug”gem时，bundle告诉我它不会安装在Ruby 1.9.3上，当我按照Heroku的建议将“debugger”gem放在gem文件的开发组中时，我仍然会收到相同的错误。 我也更新

  • 我在heroku中部署应用程序时出错

    错误：命令错误，退出状态为1:Command://app/.heroku/python/bin/python/app/.heroku/python/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel/tmp/tmp3b4z4ntu cwd://tmp/pip-i

  • 在heroku上部署Rails应用程序：获取路径错误

    我正在heroku上部署我的rails应用程序，我遇到了一个问题。 我得到这个错误 2015-04-28T05:10:29.159894 00:00 heroku[router]： at=info方法=GET路径="/欢迎/索引"主机=still-dawn-6484.herokuapp.comrequest_id=45bf4295-d7f0-4788-9f4d-be35cce41aa1 fwd="

  • 将vue应用程序部署到heroku时出错

    我有一个vuejs应用程序，它是用vue cli设置的，我正在尝试将我的应用程序部署到Heroku。 这是我的服务器： 我从gitignore中删除dist, 我在package.json中添加了一个类似“start”的起始点：“node server.js” 以下是我在控制台看到的内容： 加载资源失败：服务器响应，状态为503（服务不可用）/Favicon.ico:1 以下是heroku日志：

  • 将node.js应用程序部署到Heroku时出错

    在Heroku上部署Node.js应用程序时，我遇到以下错误。 2017-04-18T18:40:10.158442+00:00APP[Web1]:npm错误！请在任何支持请求中包含以下文件： 2017-04-18T18:40:10.158544+00:00APP[Web1]:npm错误！/app/npm-debug.log 2017-04-18T18:40:10.237236+00:00 Her

  • 如何修复部署Rails应用程序到heroku时的错误？

    我正试图将Rails应用程序部署到heroku，但出现了一个错误，如下所示。我也在整理我的档案。 宝石文件将保留安装在 /tmp/build_232b9vaemz20q/vendor/bundle/ruby/1.9.1/gems/sqlite3-1.3.7以供检查。结果记录到 /tmp/build_232b9vaemz20q/vendor/bundle/ruby/1.9.1/gems/sqlite

相关问答

将node.js应用程序部署到Heroku时出错如何修复部署Rails应用程序到heroku时的错误？在GlassFish4.1上部署应用程序时出错部署 heroku 应用程序时应用程序失败部署django应用程序时出现Heroku H10错误

相关文章

如何将使用grunt的节点应用程序部署到heroku使用IE8浏览器在jboss部署的应用程序上出现ClientAbortException在 Ubuntu 12.04 Server 上安装部署 Ruby on Rails 应用用Heroku部署Flask在Android手机上部署应用程序时找不到java.time.LocalDateTime的类

相关阅读

Flask部署redis部署入侵Web应用程序HTML5 应用程序缓存GWT 应用程序调试

相关工具

Pumadianping pumaios应用程序开发框架HerokuRails

相关文档

马上着手开发 iOS 应用程序Ruby on Rails 教程部署 kubernetes 集群Perl 程序员应该知道的事Rails 102
快捷导航： 新手教程 算法原理 架构设计 Java进阶 数据库进阶 大厂专栏 面试经验 编程笔记 编程问答 所有专题 文档资料 工具软件 电子书籍 小牛导航
在线工具： 房贷计算器 个税计算器 Linux命令查询 Json格式化 正则表达式 颜色转换 AES加解密 SHA1加密 MD5加密 毒鸡汤 字数统计 随机密码生成 进制转换 Base64编解码 励志句子
Copyright © 2019-2024 小牛知识库@xnip.cn. All Rights Reserved.