问题标签 [ruby-enterprise-edition]

我们在内部使用 Phusion 堆栈（Passenger和Ruby Enterprise Edition）取得了很好的成果，但我无法找到很多关于它们在野外使用的数据，尤其是 REE。我喜欢类似于 WWR 的High Profile Organizations Using Rails或 Ben Forta 的Who's Using ColdFusion？列表。

在这方面有一些谷歌小组活动，但我正在寻找更多的东西，因为没有更好的词，PHB 友好。

我刚刚安装了 Ruby Enterprise Edition 并正在为它安装一些 gem。Stock Ruby 1.8.6 也安装在服务器上。

我已经/opt/ruby-enterprise-1.8.6-20090201/bin在我PATH的头上添加了/usr/bin哪里ruby和gem住的地方。

which gem证实了这一点：

/opt/ruby-enterprise-1.8.6-20090201/bin/gem

但是，当我像这样安装 gem 时：

gem install some_gem

他们最终在/usr/lib/ruby/gems/1.8/gems/而不是/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/.

但如果我使用/opt/ruby-enterprise-1.8.6-20090201/bin/gem install some_gem它确实会进入 REE 的 gem 目录。

我不明白。我必须更改一些配置选项吗？我在这里使用 sudo。也许这与它有关？

我刚刚在 Ubuntu Hardy 8.04 VPS 上安装了 Ruby Enterprise Edition 和 Passenger。据我所知，安装成功。我的 Rails 应用程序是可访问的，并且总体上运行良好。但是，我的应用程序中用户可以使用 AJAX 发表评论的部分不起作用。根据Railscasts 第 65 集，我的Comment模型有一个请求的 setter 方法：

在开发中一切正常，但在生产中永远不会调用此方法，并且在尝试发表评论时出现 HTTP 500 错误。我的生产日志如下所示。

我对如何调试这个有点不知所措，所以不胜感激任何指针！我不知道是什么试图用一种方法对Fixnum班级进行猴子修补。each

编辑：事实证明，Hoptoad 异常通知程序存在一个已知问题，可以解释该Fixnum问题。它仍然没有解释为什么我的请求设置器没有被 REE 调用！

生产日志

8 月 8 日 17:06:14 railsapp rails[4666]: "\nNoMethodError (未定义方法each' for 1:Fixnum):\n passenger (2.2.4) lib/phusion_passenger/rack/request_handler.rb:91:inprocess_request'\n 乘客 (2.2.4) lib/phusion_passenger/abstract_request_handler.rb:206:in main_loop'\n passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:376:instart_request_handler'\n 乘客 (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:334:in handle_spawn_application'\n passenger (2.2.4) lib/phusion_passenger/utils.rb:182:insafe_fork'\n 乘客 (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:332:in handle_spawn_application'\n passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:insend '\n 乘客 (2.2.4) lib/phusion_passenger/ abstract_server.rb:351:in main_loop'\n passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:195:instart_synchronously'\n 乘客 (2.2.4) lib/phusion_passenger/abstract_server.rb:162:in start'\n passenger (2.2.4) lib/phusion_passenger/railz/application_spawner.rb:213:instart'\n 乘客 (2.2.4) lib/phusion_passenger/spawn_manager.rb:261:in spawn_rails_application'\n passenger (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:126:inlookup_or_add '\n 乘客 (2.2.4) lib/phusion_passenger/spawn_manager.rb:255:inspawn_rails_application'\n passenger (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:80:in同步'\n 乘客 (2.2.4) lib/phusion_passenger/abstract_server_collection.rb:79:in synchronize'\n passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:254:inspawn_rails_application'\n 乘客 (2.2.4) lib/phusion_passenger/spawn_manager.rb:153:in spawn_application'\n passenger (2.2.4) lib/phusion_passenger/spawn_manager.rb:286:inhandle_spawn_application'\n 乘客 (2.2. 4) lib/phusion_passenger/abstract_server.rb:351:in __send__'\n passenger (2.2.4) lib/phusion_passenger/abstract_server.rb:351:inmain_loop'\n 乘客 (2.2.4) lib/phusion_passenger/abstract_server.rb:195:in start_synchronously'\n\n" Aug 08 17:06:14 railsapp rails[4666]: "/!\\ FAILSAFE /!\\ Sat Aug 08 17:06:14 +0000 2009\n Status: 500 Internal Server Error\n undefined methodeach' for 1:Fixnum\n /opt/ruby-enterprise-1.8 .6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:489:in filter_parameters'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:496:infilter_parameters'\n /opt/ruby-enterprise-1.8.6-20090610/lib /ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:495:incollect'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:495:infilter_parameters'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:489:in each'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:489:infilter_parameters'\n /home /deploy/public_html/railsapp/releases/20090808155352/vendor/plugins/hoptoad_notifier/lib/hoptoad_notifier.rb:309:in notify_hoptoad clean_notice'\n /home/deploy/public_html/railsapp/releases/20090808155352/vendor/plugins/hoptoad_notifier/lib/hoptoad_notifier.rb:235:in'\n /home/deploy/public_html/railsapp/releases/20090808155352/vendor/plugins/hoptoad_notifier/lib /hoptoad_notifier.rb:226:in rescue_action_in_public'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/rescue.rb:154:inrescue_action_without_handler'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/rescue.rb:74 :inrescue_action'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:527:in发送'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/base.rb:527:inprocess_without_filters'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/filters.rb:606:in进程'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/rescue.rb:65:in call_with_exception'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/dispatcher.rb:91:indispatch'\n /opt /ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/dispatcher.rb:111:in _call'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/dispatcher.rb:82:ininitialize'\n /opt/ruby-enterprise-1.8 .6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/head.rb:9:in call'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/head.rb:9:incall'\n /opt/ruby -enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/methodoverride.rb:24:in call'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/params_parser.rb:15:incall'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/session/abstract_store.rb:122:incall'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/query_cache.rb:29:in调用'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in cache'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/query_cache.rb:9:incache' \n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/query_cache.rb:28:in call'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:incall'\n /opt/ruby -enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/failsafe.rb:26:in call'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:incall'\n /opt/ruby-enterprise-1.8.6 -20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:in synchronize'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/vendor/rack-1.0.0-git/lib/rack/lock.rb:11:incall'\n /opt/ruby-enterprise -1.8.6-20090610/lib/ruby/gems/1.8/gems/actionpack-2.3.3/lib/action_controller/dispatcher.rb:106:incall'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/rack/request_handler.rb:91:inprocess_request'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_request_handler.rb:206:in main_loop'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb:376:instart_request_handler'\n /opt /ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb:334:in handle_spawn_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/utils.rb:182:insafe_fork'\n /opt/ruby-enterprise -1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb:332:in handle_spawn_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:insend '\n /opt/ruby-enterprise-1.8.6 -20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in main_loop'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:instart_synchronously'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby /gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:162:instart'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/railz/application_spawner.rb:213:in开始'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:261:in spawn_rails_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server_collection.rb:126:inlookup_or_add'\n /opt /ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:255:in spawn_rails_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server_collection.rb:80:insynchronize'\n /opt/ruby-enterprise-1.8 .6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server_collection.rb:79:in synchronize'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:254:inspawn_rails_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib /ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:153:in spawn_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/spawn_manager.rb:286:inhandle_spawn_application'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8 /gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:in__send__'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:351:inmain_loop'\n /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/lib/phusion_passenger/abstract_server.rb:195:in `start_synchronously'\n / opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/passenger-2.2.4/bin/

因此，安装 Ruby 企业版相当顺利（除了我所使用的系统的一个非常奇怪的怪癖，apt-get install build-essentials因为没有 GCC，我不得不这样做......），但它未能正确安装任何数据库 gem。我主要想用MySQL。这是 mysql gem 安装期间 Ruby EE 的 ./installer 的输出：

显然我的服务器的 MySQL 安装没有附带源代码，所以我不能只是重新编译并希望它能工作......我试图下载版本并编译它，但我不知道从这里做什么。有任何想法吗？MySQL 已经在这个服务器上运行了很多数据库，所以我也不想弄乱这里已经存在的东西......

我在 Debian Lenny 上全新安装了 Ruby EE (1.8.6-20090610) 和 Passenger (2.2.5)。REE 安装在 /opt/ruby-enterprise 并通过 /etc/environment 添加到所有用户的 $PATH 中，PassengerDefaultUser 设置为 root。问题是在加载 rails 应用程序时，Passenger 错误说 rails 2.3.3 gem 丢失。然而，它安装了Passenger和一个rails -v，因为root说它在那里。可能出了什么问题？

我计划建立一个网站，它将是一个简单的 CMS，用户可以在其中提交和查看包含视频、照片和文本的帖子。

我想做的一个决定是在 Ruby Enterprise Edition 和 Ruby 1.9 之间进行选择。

我关心的事情是：

1. 性能和可扩展性。
2. 与现有 gems/plugins/开源项目的兼容性。
3. 开发和部署速度（我将在 VPS 上部署）。

你的建议是什么？

我正在运行 Rails 2.3.3 应用程序，该应用程序使用乘客/mod_rails 和 ruby​​-enterprise-1.8.6-20090610 和 apache httpd 进行部署。

问题是每当我部署我们的应用程序时，数百个 httpd 进程开始死亡。我收到此错误：

短时间10-20min后。这些错误消失了。

这个问题是在将我们的数据库迁移到单独的专用机器后开始的。所以我认为这可能是 mysql-db 连接池和管理的问题，但是我无法定义它。

有没有人可以帮助我解决这个问题，或者只是给我一个线索如何更深入地调试它。先感谢您。

有没有办法确定 Rails 中运行的是哪个版本的 Ruby（在网络上或通过script/console）？我安装了 Ruby 1.8.6，但我还安装了 Ruby Enterprise Edition 1.8.7-20090928，并希望确保它使用正确的安装。

我遇到了一个非常奇怪的错误。我在 Solaris 10 上，使用 Ruby Enterprise Edition (ruby 1.8.6 (2008-08-08 patchlevel 286) [i386-solaris2.10]) 和 Rails 2.3.4。我有一个非常奇怪的错误。在 irb 中：

一切安好！但是当我启动 Rails 控制台并做同样的事情时，“to_f”总是返回“0,0”。

当我在我的 Mac 上做同样的事情时，这不会发生。很奇怪！这可能是 Ruby 企业版中的错误吗？但如果是这样，为什么 irb 不会出现（这也是 REE 版本，我仔细检查了）。有任何想法吗？

• 约翰内斯

最近我似乎注意到了一些 RoR 开发人员的趋势，即在他们的开发过程中使用 RubyEE/Passenger/Apache 类型设置。

除了明显的“使用您的客户使用的东西”的想法之外，与 vanilla mongrel 堆栈给您的相比，这些技术是否以任何方式增强了开发环境？