FYI - I found a way to stop the process...

http://railstips.org/2007/2/12/oops-i-did-it-again

comand line... (shows your process)
ps aux | grep script/server
sudo kill -9 XXXX (kill your process X is the PID)


On Nov 29, 2:40 pm, pixelhandler <[EMAIL PROTECTED]> wrote:
> I'm going thru a tutorial, Agile Web Development with Rails (v3)...
>
> I'm having an issue on my mac with the web server not quitting
> properly,mongrel/webrickprocess not shutting down properly in dev
> env. after ^C in terminal window. On subsequent attempts to restart
> the web server after quit.. ruby script/serverwebrick
>
> I also notice that when I update a file in the app folder I have to
> restart the app on another port.
>
> I get an error...
>
> => BootingWEBrick...
> => Rails 2.1.1 application started onhttp://0.0.0.0:3000
> => Ctrl-C to shutdown server; call with --help for options
> [2008-11-29 13:53:39] INFO  WEBrick1.3.1
> [2008-11-29 13:53:39] INFO  ruby 1.8.6 (2008-03-03) [powerpc-
> darwin9.2.2]
> [2008-11-29 13:53:39] WARN  TCPServer Error: Address already in use -
> bind(2)
> /opt/local/lib/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)
> ...
>
> Dev Env:
> - OSX 10.5, with default Ruby, 1.8.6
> - Rails 2.2.2 (have multiple version installed) tutorial uses 2.1.1
>         - create app with... rails _2.1.1_ depot
> - updated gems 1.1.1
>         --system /mongrel/webrick
>
> Thanks for any thoughts on fixing this issue :)
>
> Best regards,
> --
> Bill Heaton
> [blog]        http://pixelhandler.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to