blocks|key|969477|text|我可能会因为回避这个问题而被否决，但我最近从nginx+%2B+mongrel转到了mod_rails，这真的给我留下了深刻的印象。移动到一个简单得多的设置无疑会在未来省去我的头疼。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|969478|这是一个非常简单的过渡，我强烈推荐它。|969479|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I might get voted down for dodging the question, but I recently moved from nginx + mongrel to mod_rails and have been really impressed. Moving to a much simpler setup will undoubtedly save me headaches in the future. 

It was a really easy transition, I'd highly recommend it.

blocks|key|735965|text|你确定问题是由Mongrel引起的吗？您是否尝试过在WEBrick下运行您的应用程序？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735966|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Are you sure the problem is caused by Mongrel? Have you tried running your application under WEBrick?

blocks|key|4519834|text|虽然有a+few+things+you+can+check，但由于您说日志中没有任何指示错误的内容，因此在使用Logger类的日志循环特性时，听起来可能会遇到错误。它会导致mongrel锁定。考虑使用logrotate或其他一些外部日志轮换服务，而不是依赖Logger来轮换日志。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4519835|entityMap|0|LINK|mutability|MUTABLE|url|http://mongrel.rubyforge.org/wiki/FAQ#Q:WhatcancauseMongreltolockuponaregularbasis^0|1J|6|2S|9|3K|6|3|Q|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

There are <a href="http://mongrel.rubyforge.org/wiki/FAQ#Q:WhatcancauseMongreltolockuponaregularbasis" rel="nofollow noreferrer">a few things you can check</a>, but since you say there's nothing in the logs to indicate error, it sounds like you might be running into a bug when using the log rotation feature of the <code>Logger</code> class. It causes mongrel to lock up. Instead of relying on <code>Logger</code> to rotate your logs, consider using <code>logrotate</code> or some other external log rotation service.

blocks|key|4519844|text|这种情况是否每次都会在设定的小时数/天数发生？你有多少内存？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4519845|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Does this happen at a set number of hours/days every time? How much RAM do you have?

blocks|key|3051949|text|我也有同样的问题。我将范围缩小到的两个选项都与MySQL适配器相关。我在Red+Hat+Enterprise+Linux+4(或5)上运行，应用程序在给定的空闲时间后会挂起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3051950|一个建议的解决方案是编译原生MySQL绑定，我一直在使用纯Ruby绑定。|3051951|另一种方法是在MySQL适配器上设置比连接空闲时间更长的超时时间。(我没有记录具体的配置，但我记得它是在environment.rb中，它是mysql适配器中的某个类变量。)|3051952|我不记得这两个解决方案中有没有解决这个问题的，我们在那之后不久就搬到了Ubuntu，从那以后就再也没有出现过问题。|3051953|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had this same problem. The couple options I had narrowed it down to were MySQL adapter related. I was running on Red Hat Enterprise Linux 4 (or 5) and the app would hang after a given amount of idle time.

One suggested solution was to compile native MySQL bindings, I had been using the pure Ruby one.

The other was to set the timeout on the MySQL adapter higher than what the connection would idle out on. (I don't have the specific configuration recorded, but as I recall it was in environment.rb and it was some class variable in the mysql adapter.)

I don't recall if either of those solutions fixed it, we moved to Ubuntu shortly after that and hadn't had a problem since.

blocks|key|3052047|text|查看Mongrel常见问题解答：http://mongrel.rubyforge.org/wiki/FAQ|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3052048|根据我的经验，在以下情况下，mongrel会挂起：|3052049|3052050|日志文件太大(几百兆字节)。您必须设置日志轮换。|unordered-list-item|3052051|+MySQL驱动程序超时您必须更改MySQL驱动程序的超时设置，方法是将以下内容添加到您的environment.rb：ActiveRecord::Base.verification_timeout+=+14400+(在常见问题解答的部署部分中有进一步解释)|style|CODE|3052052|3052053|entityMap|0|LINK|mutability|MUTABLE|url|http://mongrel.rubyforge.org/wiki/FAQ^0|G|11|0|0|0|0|0|1O|1B|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|11|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|12|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|13|8|@$A|14|B|15|L|M]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Check the Mongrel FAQ:
<a href="http://mongrel.rubyforge.org/wiki/FAQ" rel="nofollow noreferrer">http://mongrel.rubyforge.org/wiki/FAQ</a>

From my experience, mongrel hangs when:

<ul>
<li>the log file got too big (hundreds of megabytes in size). you have to setup log rotation. </li>
<li>the MySQL driver times out
you have to change the timeout settings of your MySQL driver by adding this to your environment.rb:
<code>ActiveRecord::Base.verification_timeout = 14400</code>
(this is further explained in the deployment section of the FAQ)</li>
</ul>

blocks|key|3052098|text|我们也遇到过同样的问题。首先，安装mongrel_proctitle+gem|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3052099|http://github.com/rtomayko/mongrel_proctitle/tree/master|offset|length|3052100|这个gem/plugin将允许你通过"ps“查看混杂进程，你可以看到一个混杂进程是否挂起。我们已经看到Mongrel的一个问题是，它会很乐意地接受连接并将它们排入队列，然后楔入自己。这个插件将帮助你查看一只杂种狗何时被楔入，但之后你必须使用另一个监控应用程序来实际重启一只被楔入的杂种狗，比如Monit或God|3052101|你可能还想考虑在你的蒙古人面前放置一个更平衡的反向代理，比如HAproxy，而不是nginx，Apache或Lighttpd。在HAproxy中将“maxconn1”设置为“maxconn1”，您可以确保队列由HAproxy与Mongrel维护。其他反向代理(nginx、Apache、Lighttpd)只执行循环，这意味着它们可能会无意中加载您的Mongrel队列。|3052102|我个人的选择是上帝，因为它更灵活。|3052103|tl;dr安装这个gem插件，注意你的蒙古人。试试Apache%2BPhusion+Passenger吧。|3052104|entityMap|0|LINK|mutability|MUTABLE|url|1|http://mmonit.com/monit/|2|http://god.rubyforge.org/^0|0|0|1K|0|0|42|5|1|48|3|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]|$D|17|E|18|1|19]]|A|$]]|$1|H|3|I|5|6|7|1A|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1B|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|C]]|U|$5|Q|R|S|A|$T|V]]|W|$5|Q|R|S|A|$T|X]]]]

We have experienced this same issue. First off, install the mongrel_proctitle gem

<a href="http://github.com/rtomayko/mongrel_proctitle/tree/master" rel="nofollow noreferrer">http://github.com/rtomayko/mongrel_proctitle/tree/master</a>

This gem/plugin will allow you to view the mongrel processes via "ps" and you can see if a Mongrel is hung. An issue we have seen with Mongrel is that it will happily accept connections and enqueue them, then wedge itself. This plugin will help you see when a Mongrel has been wedged but then you must use another monitoring app to actually restart a a wedged Mongrel, something like <a href="http://mmonit.com/monit/" rel="nofollow noreferrer">Monit</a> or <a href="http://god.rubyforge.org/" rel="nofollow noreferrer">God</a>

You might also want to consider putting a more balanced reverse proxy in front of your Mongrels, something HAproxy, instead of nginx, Apache or Lighttpd. With a setting of "maxconn 1" in HAproxy you can assure that the queue is being maintained by HAproxy versus Mongrel. The other reverse proxies (nginx, Apache, Lighttpd) only do round-robin which means that they can load up your Mongrel queue, inadvertently.

My personal choice is God as it is much more flexible.

tl;dr Install this gem plugin and keep an eye on your Mongrels. Try Apache+Phusion Passenger.

blocks|key|963352|text|不幸的是，随着时间的推移，Rails+(以及Mongrel)使用了太多的内存，崩溃是一个众所周知的问题(50K%2B谷歌词条中的"Ruby，rails，crashing，memory")。当前的ruby解释器具有sometimes+simply+fails+entirely+to+give+memory+back+to+the+system的特性-它可以重用它拥有的内存，但它不会放弃它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|963353|在生产环境中监控、杀死和重启Mongrel实例的方案有很多，例如：(随机选择)+rails+monitor。在问题得到更果断的解决之前，其中一个可能是您最好的选择。|963354|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ruby-forum.com/topic/121254|1|http://kontsevoy.com/rails-monitor/^0|2W|1T|0|0|14|D|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Unfortunately, Rails (and thereby Mongrel) using up too much memory over time and crashing is a known problem (50K+ Google entries for "Ruby, rails, crashing, memory"). The current ruby interpreter has the property that it <a href="http://www.ruby-forum.com/topic/121254" rel="nofollow noreferrer">sometimes simply fails entirely to give memory back to the system</a> - it may reuse the memory it has but it won't give it up. 

There are numerous schemes for monitoring, killing and restarting Mongrel instances in a production environment - for example: (choosing at random) <a href="http://kontsevoy.com/rails-monitor/" rel="nofollow noreferrer">rails monitor</a> . Until the problem is fixed more decisively, one of these may be your best bet.

I'm running into a problem in a Rails application. 
After some hours, the application seems to start hanging, and I wasn't able to find where the problem was. There was nothing relevant in the log files, but when I tried to get the url from a browser nothing happened (like mongrel accept the request but wasn't able to respond).

What do you think I can test to understand where the problem is? 

Thanks for your help!

Mongrel hangs

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在Rails应用程序中遇到了一个问题。几个小时后，应用程序似乎开始挂起，我找不到问题所在。日志文件中没有任何相关内容，但是当我试图从浏览器获取url时，什么也没有发生(比如mongrel接受了请求，但无法响应)。您认为我可以通过哪些测试来了解问题所在？谢谢你的帮忙!

问Mongrel挂起
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mongrel挂起EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mongrel挂起
EN