I’m able to start Webrick per the below results:
$ ruby script/server
=> Booting WEBrick
=> Rails 2.3.5 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2010-05-07 16:26:35] INFO WEBrick 1.3.1
[2010-05-07 16:26:35] INFO ruby 1.8.7 (2008-08-11) [i386-cygwin]
[2010-05-07 16:26:35] INFO WEBrick::HTTPServer#start: pid=6496
port=3000
However when I go to http://localhost:3000/ the page never loads.
It’s continues to try to load but never completes (meaning I don’t
even get an error in connection message)
If I do a ‘Ctrl+C’ on the console, the server never exits or
shutdowns.
What’s interesting is that I then open another console and start
Webrick again per the below results:
$ ruby script/server -p 8080
=> Booting WEBrick
=> Rails 2.3.5 application starting on http://0.0.0.0:8080
=> Call with -d to detach
=> Ctrl-C to shutdown server
[2010-05-07 16:32:30] INFO WEBrick 1.3.1
[2010-05-07 16:32:30] INFO ruby 1.8.7 (2008-08-11) [i386-cygwin]
[2010-05-07 16:32:30] INFO WEBrick::HTTPServer#start: pid=7800
port=8080
This time when I go to http://localhost:8080/ I get the ‘Welcome
Aboard’ page indicating server is running. This all happens while the
first console seems frozen after ‘ctrl+C’. and the second console
running webrick on port 8080.
I’m not sure if the ports have anything to do with the difference as I
have tried 8080 first and 3000 second. In either case the second run
of the webrick server works (port 3000) while the first run freezes
(port 8080).
Why do I have to run the webserver twice to get the browser to
indicate server is up and running?
Any ideas would be great to hear.
Thanks in advance.