[Mongrel] Mongrel Processes Dying
Daniel.Berger at qwest.com
Tue Sep 26 14:08:10 EDT 2006
Zed A. Shaw wrote:
> On Tue, 26 Sep 2006 05:50:37 -0700
> mongrel_users at homerlex.mailshell.com wrote:
>> We are seeing mongrel processes dying in our mongrel cluster. What is the best way to
>> troubleshoot this?
>> We have ruby 1.8.4, Rails 1.1.0 (upgrading soon), MySql 4.1 running on Red Hat Enterprise Linux
>> ES release 4, Apache 2.2, mongrel-0.3.13.3, mongrel_cluster-0.2.0
>> I saw the following messages in the mongrel.log but not sure if theay are related to the
>> processes dying. It would be nice if the log had date/time for each entry!
>> /usr/local/lib/ruby/1.8/net/http.rb:562: [BUG] Segmentation fault
>> ruby 1.8.4 (2005-12-24) [i686-linux]
> These are segmentation faults inside Ruby's http code. Not sure how you're getting those but you'll need to investigate how your system is apparently totally different from everyone else's. For example, why is it in /usr/local? I'm thinking maybe you're mixing ruby installations/versions.
> And, it's really hard to change http.rb to produce timestamps during a segfault. Actually the fact that ruby is giving you a line number is pretty magical, so be thankful. Normally you'd have to gdb a core file for that.
> Which brings up another thing, turn on core dumps and that might help track it down.
I did notice that there were some fixes for http.rb in the ChangeLog for 1.8.5.
I don't know if upgrading is an option, but you may want to consider it.
Mind you, given that the problem ultimately seems to be coming from TCPSocket,
I'm not sure if they'll help.
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
More information about the Mongrel-users