# Problem starting mongrel server

**URL:** <https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840>\
**Category:** Rails\
**Created:** [November 11, 2008, 1:56am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840 "2008-11-11T01:56:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 11, 2008, 1:56am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/1 "2008-11-11T01:56:33Z")

</div>

Hi, I am newbie started learning ruby on rails i had an application  
which used to run pretty well latter i upgraded from webbrick to mongrel  
1.1.5 then I am getting the  
foloowing errors and a default application runs on port 3000 by name  
iphone configuration utility  
i am unable to attach the screen shot as it is saying file to large.  
Error which i get in terminal is listed below

=\> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)  
=\> Rails application starting on [http://0.0.0.0:3000](http://0.0.0.0:3000)  
=\> Call with -d to detach  
=\> Ctrl-C to shutdown server  
\*\* Starting Mongrel listening at 0.0.0.0:3000  
Exiting  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in  
`initialize_without_backlog': Address already in use - bind(2) (Errno::EADDRINUSE) from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in `initialize’  
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:in  
`new' from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:in `initialize’  
from  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:139:in  
`new' from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:139:in `listener’  
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/mongrel\_rails:99:in  
`cloaker_' from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:50:in `call’  
from  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:50:in  
`initialize' ... 14 levels... from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/commands/server.rb:39 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem\_original\_require’  
from /Library/Ruby/Site/1.8/rubygems/custom\_require.rb:27:in `require’  
from ./script/server:3

Thanks & Regards  
Chandu

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 11, 2008, 2:46am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/2 "2008-11-11T02:46:19Z")

</div>

On Nov 11, 11:56 am, Chandu C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> =\> Call with -d to detach  
> =\> Ctrl-C to shutdown server  
> \*\* Starting Mongrel listening at 0.0.0.0:3000  
> Exiting  
> /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in  
> `initialize\_without\_backlog’: Address already in use - bind(2)  
> (Errno::EADDRINUSE)

You already have a program listening on port 3000 probably an earlier  
webrick or mongrel. If you didn’t detach it, then find it and stop  
it.  
If it’s detached you need to find its pid and kill it.  
I’m not sure what system you’re using; to see what’s running on port  
3000 try:  
netstat -4np (linux)  
sockstat -4 (bsd)  
netstat -nb (windows - there’s probably a better way here, I don’t use  
windows for rails)  
Get the pid from the listing and kill it if it’s ok to do that.

–  
Daniel B.

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 11, 2008, 11:13am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/3 "2008-11-11T11:13:04Z")

</div>

This can also be caused by having a Windows Mobile plugged in to the  
PC with ActiveSync running

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 11, 2008, 12:57pm UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/4 "2008-11-11T12:57:48Z")

</div>

kill running process called ruby.exe then start your server it wil  
work…

regards  
abhi

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 12, 2008, 2:07am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/5 "2008-11-12T02:07:27Z")

</div>

Daniel B. wrote:

> On Nov 11, 11:56ï¿½am, Chandu C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> wrote:
> 
> > =\> Call with -d to detach  
> > =\> Ctrl-C to shutdown server  
> > \*\* Starting Mongrel listening at 0.0.0.0:3000  
> > Exiting  
> > /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in  
> > `initialize\_without\_backlog’: Address already in use - bind(2)  
> > (Errno::EADDRINUSE)
> 
> You already have a program listening on port 3000 probably an earlier  
> webrick or mongrel. If you didn’t detach it, then find it and stop  
> it.  
> If it’s detached you need to find its pid and kill it.  
> I’m not sure what system you’re using; to see what’s running on port  
> 3000 try:  
> netstat -4np (linux)  
> sockstat -4 (bsd)  
> netstat -nb (windows - there’s probably a better way here, I don’t use  
> windows for rails)  
> Get the pid from the listing and kill it if it’s ok to do that.
> 
> –  
> Daniel B.

Hi, my sys config is mac-os-x 10.5.5 i tried to kill process runnig on  
port 3000 by using top command but but the problem is not solved it  
repeats again i have an interview scheduled this week dont know by the  
time whther it might be solved or not…

Thanks 4 all Replies

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 12, 2008, 6:22am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/6 "2008-11-12T06:22:30Z")

</div>

Then run on diff port using  
script/server -p 3001

regards  
Abhi

On Wed, Nov 12, 2008 at 7:12 AM, Frederick C. \<

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [November 12, 2008, 2:43am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/7 "2008-11-12T02:43:11Z")

</div>

On 12 Nov 2008, at 01:07, Chandu C. wrote:

> 

> > –  
> > Daniel B.
> 
> Hi, my sys config is mac-os-x 10.5.5 i tried to kill process runnig on  
> port 3000 by using top command but but the problem is not solved it  
> repeats again i have an interview scheduled this week dont know by the  
> time whther it might be solved or not…

netstat -f inet

Will show who is listening on whatever port on a mac.

Fred

---

<div class="post-metadata">

**Author:** ![chandu4ruby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/df788c/32.png) [@chandu4ruby](https://www.ruby-forum.com/u/chandu4ruby)\
**Post date:** [March 30, 2009, 6:18am UTC](https://www.ruby-forum.com/t/problem-starting-mongrel-server/196840/8 "2009-03-30T06:18:15Z")

</div>

Abhishek shukla wrote:

> kill running process called ruby.exe then start your server it wil  
> work…
> 
> regards  
> abhi

Try this

On Mac OS X:

ps -U |grep ruby

look for

39704 ttys001 0:01.63 ruby ./script/server

where 39704 is the PID, then

sudo kill -9 39704

replace 39704 with your PID

Now you can ./script/server from your app root.
