# Ruby 1.8.7p249 + rails 2.3.5 + Snow Leopard = hung processes?

**URL:** <https://www.ruby-forum.com/t/ruby-1-8-7p249-rails-2-3-5-snow-leopard-hung-processes/186661>\
**Category:** Rails\
**Created:** [April 10, 2010, 10:17pm UTC](https://www.ruby-forum.com/t/ruby-1-8-7p249-rails-2-3-5-snow-leopard-hung-processes/186661 "2010-04-10T22:17:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![markds75](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a4c791/32.png) [@markds75](https://www.ruby-forum.com/u/markds75)\
**Post date:** [April 10, 2010, 10:17pm UTC](https://www.ruby-forum.com/t/ruby-1-8-7p249-rails-2-3-5-snow-leopard-hung-processes/186661/1 "2010-04-10T22:17:29Z")

</div>

A few weeks ago I updated my development computer to Snow Leopard  
(finally). I put it off because I was in the middle of a project, and  
it seems its a good thing I did. Last week I started something new and  
it seems that any rails related ruby process will get … stuck, I  
guess is the best word. I’ve seen it happen as soon as a minute, or  
take as long as an hour. It happens for script/server and script/  
runner based processes; as far as I’ve been able to tell, it doesn’t  
happen with pure ruby processes, but then again the test script I used  
wasn’t trying to do things like connect to a MySQL DB. When the  
processes get stuck, control-c does not stop them, they have to be  
forced to quit with “kill -9”.

Has anyone else seen this?

Thanks!

Mark

Some info from my environment…

> ruby --version  
> ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10.2.0]

> env | grep RUBY  
> RUBYOPT=rubygems

> mysql --version  
> mysql Ver 14.14 Distrib 5.1.44, for apple-darwin10.2.0 (i386) using  
> readline 5.1

> gem list --local  
> actionmailer (2.3.5, 2.1.1)  
> actionpack (2.3.5, 2.1.1)  
> activerecord (2.3.5, 2.1.1)  
> activeresource (2.3.5, 2.1.1)  
> activesupport (2.3.5, 2.1.1)  
> …  
> mongrel (1.1.5)  
> mysql (2.8.1)  
> …  
> rails (2.3.5, 2.1.1)  
> rake (0.8.7, 0.8.3)  
> …  
> rubyforge (2.0.3, 1.0.1)  
> rubygems-update (1.3.6, 1.3.5)  
> …

> gem --version  
> 1.3.6

---

<div class="post-metadata">

**Author:** ![markds75](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/a4c791/32.png) [@markds75](https://www.ruby-forum.com/u/markds75)\
**Post date:** [April 10, 2010, 10:48pm UTC](https://www.ruby-forum.com/t/ruby-1-8-7p249-rails-2-3-5-snow-leopard-hung-processes/186661/2 "2010-04-10T22:48:31Z")

</div>

I found this blog article just after posting:  
[http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/](http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/)

I figured I’d try his fix for mongrel, which involves uninstalling the  
gem and re-installing it. But whenever I try to run “sudo gem install  
mongrel”, the gem process seems to hang. I’ve had it running for 10  
minutes now, and with verbose output turned on, this is all its said:

> sudo gem install --verbose mongrel  
> GET [RubyGems.org | your community gem host](http://gems.rubyforge.org/latest_specs.4.8.gz)  
> 302 Found  
> GET [http://production.s3.rubygems.org/latest\_specs.4.8.gz](http://production.s3.rubygems.org/latest_specs.4.8.gz)

I was able to access  
[http://production.s3.rubygems.org/latest\_specs.4.8.gz](http://production.s3.rubygems.org/latest_specs.4.8.gz)  
in my browser and the file downloaded in a few seconds, so I doubt  
that’s the issue.

At the same time, I was able to run “sudo gem install thin” and there  
were no problems.

Mark