<div>Hi Nii,</div>
<div> </div>
<div>Looks like something else is already running on the port that Mongrel wants, 3000 by default. See if you have any other mongrels running (ps -ef) or better yet, bring up <a href="http://localhost:3000/">http://localhost:3000
</a> and see what's running.</div>
<div> </div>
<div>Michael<br><br></div>
<div class="gmail_quote">On Dec 11, 2007 10:19 AM, Nii Amon Dsane <<a href="mailto:jazzyy@gmail.com">jazzyy@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi
<div><br></div>
<div>I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving.</div>
<div><br></div>
<div>I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6. It was all working fine and starting as expected. But I did a server reboot once and mongrel has refused to start up since. I get the following error:
</div>
<div><br></div>
<div>
<div>/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/../lib/mongrel/tcphack.rb:12:in `initialize_without_backlog': Cannot assign requested address - bind(2) (Errno::EADDRNOTAVAIL) </div>
<div> from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/../lib/mongrel/tcphack.rb:12:in `initialize'</div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:865:in `open'</div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:865:in `open_server' </div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:759:in `open_server'</div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:757:in `each'</div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:757:in `open_server' </div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:1339:in `initialize'</div>
<div> from /usr/lib/ruby/1.8/drb/drb.rb:1627:in `new'</div>
<div> ... 31 levels...</div>
<div> from /usr/lib/ruby/gems/1.8/gems/mongrel- 1.1.1/bin/../lib/mongrel/command.rb:212:in `run'</div>
<div> from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/mongrel_rails:281</div>
<div> from /usr/bin/mongrel_rails:16:in `load'</div>
<div> from /usr/bin/mongrel_rails:16 </div>
<div><br></div>
<div>Initially I though that it was due to the fact that somehow there were processes that were holding onto the ports so I did a netstat to check for listening processes. However there were no processes holding onto the ports.
</div>
<div><br></div>
<div>I suspect that it is something that is in the configuration for that particular application because there are other applications on the server which are still working fine. </div>
<div><br></div>
<div>Has anyone else experienced this before and what was the resolution.</div>
<div><br></div>
<div>Thanks</div>
<div>Nii Amon</div></div><br>_______________________________________________<br>Mongrel-users mailing list<br><a href="mailto:Mongrel-users@rubyforge.org">Mongrel-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/mongrel-users" target="_blank">
http://rubyforge.org/mailman/listinfo/mongrel-users</a><br></blockquote></div><br>