# Mongrel error since updating to OSX 10.5.3

**URL:** <https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085>\
**Category:** Mongrel\
**Created:** [May 30, 2008, 5:36pm UTC](https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085 "2008-05-30T17:36:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Daw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@Matt\_Daw](https://www.ruby-forum.com/u/Matt_Daw)\
**Post date:** [May 30, 2008, 5:36pm UTC](https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085/1 "2008-05-30T17:36:14Z")

</div>

Howdy, I’m getting an error message when trying to run one of my rails  
apps, which seems to have started after updating to 10.5.3.

mattdaw-2:v1.5\_patch mdaw$ mongrel\_rails start  
\*\* Starting Mongrel listening at 0.0.0.0:3000  
\*\* Starting Rails with development environment…  
/usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/  
lib/mongrel/tcphack.rb:12:in `initialize_without_backlog': getaddrinfo: nodename nor servname provided, or not known (SocketError) from /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/ mongrel-1.1.5/bin/../lib/mongrel/tcphack.rb:12:in`initialize’  
from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:865:in  
`open' from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:865:in`open\_server’  
from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:759:in  
`open_server' from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:757:in`each’  
from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:757:in  
`open_server' from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:1339:in`initialize’  
from /usr/local/ruby-patched/lib/ruby/1.8/drb/drb.rb:1627:in  
`new' ... 29 levels... from /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/ mongrel-1.1.5/bin/../lib/mongrel/command.rb:212:in`run’  
from /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/  
mongrel-1.1.5/bin/mongrel\_rails:281  
from /usr/local/ruby/bin/mongrel\_rails:19:in `load’  
from /usr/local/ruby/bin/mongrel\_rails:19

I’m running ruby 1.8.6 (2008-03-03 patchlevel 114) [i686-darwin9.2.2]  
which I compiled myself, but another member of my team is using stock  
ruby from leopard and is getting the same behavior on this one  
application.

Any idea what could cause this? Thanks!

Matt

---

<div class="post-metadata">

**Author:** ![Matt\_Daw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@Matt\_Daw](https://www.ruby-forum.com/u/Matt_Daw)\
**Post date:** [May 30, 2008, 7:47pm UTC](https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085/2 "2008-05-30T19:47:24Z")

</div>

Matt Daw wrote:

> Howdy, I’m getting an error message when trying to run one of my rails  
> apps, which seems to have started after updating to 10.5.3.
> 
> mattdaw-2:v1.5\_patch mdaw$ mongrel\_rails start  
> \*\* Starting Mongrel listening at 0.0.0.0:3000  
> \*\* Starting Rails with development environment…  
> /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/  
> lib/mongrel/tcphack.rb:12:in `initialize\_without\_backlog’:  
> getaddrinfo: nodename nor servname provided, or not known (SocketError)

If you try running a migration it gives a better stack trace, and I  
tracked it down to backgroundrb/drb. I’m using an older version of  
backgroundrb, and on line 67 of  
vendor/plugins/backgroundrb/lib/backgroundrb.rb it calls  
DRb.start\_service(‘druby://localhost:0’). I changed that to  
DRb.start\_service(nil), which finds the first open port, and it starts  
up. I haven’t tested this at all, let alone in a production environment,  
but I will have in a few days. I’d be interested to know if this is all  
it takes to solve your problem too.

---

<div class="post-metadata">

**Author:** ![Matt\_Daw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@Matt\_Daw](https://www.ruby-forum.com/u/Matt_Daw)\
**Post date:** [May 30, 2008, 7:56pm UTC](https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085/3 "2008-05-30T19:56:12Z")

</div>

Hi Woody, thanks, that fixed it for me. That explains the difference  
in my app, the newer branches are on an up to date backgroundrb, while  
the broken one is still on an ancient one.

Matt

---

<div class="post-metadata">

**Author:** ![Matt\_Daw](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ecc23a/32.png) [@Matt\_Daw](https://www.ruby-forum.com/u/Matt_Daw)\
**Post date:** [June 2, 2008, 10:37pm UTC](https://www.ruby-forum.com/t/mongrel-error-since-updating-to-osx-10-5-3/139085/4 "2008-06-02T22:37:09Z")

</div>

Matt Daw wrote:

> Hi Woody, thanks, that fixed it for me. That explains the difference  
> in my app, the newer branches are on an up to date backgroundrb, while  
> the broken one is still on an ancient one.
> 
> Matt

Yeah, I was having the same issue and this worked for me too. Thanks for  
the tip!

-gb
