I''m having a newbie problem getting Instant Rails to start WEBrick. I''ve created a demo project by type Rails Demo at the InstantRails command prompt. This worked fine. I then navigate to the Demo directory and type ruby script/server. I get the following errors... C:\InstantRails\InstantRails\rails_apps\demo>ruby script/server => Booting WEBrick... => Rails application started on http://0.0.0.0:3000 => Ctrl-C to shutdown server; call with --help for options [2006-10-24 18:33:24] INFO WEBrick 1.3.1 [2006-10-24 18:33:24] INFO ruby 1.8.5 (2006-08-25) [i386-mswin32] [2006-10-24 18:33:24] WARN TCPServer Error: Bad file descriptor - bind(2) C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/utils.rb:73:in `initializ e'': Bad file descriptor - bind(2) (Errno::EBADF) from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/utils.rb:73: in `new'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/utils.rb:73: in `create_listeners'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/utils.rb:70: in `each'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/utils.rb:70: in `create_listeners'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/server.rb:75 :in `listen'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/server.rb:63 :in `initialize'' from C:/InstantRails/InstantRails/ruby/lib/ruby/1.8/webrick/httpserver.r b:24:in `initialize'' from C:/InstantRails/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-1.1. 6/lib/webrick_server.rb:59:in `new'' ... 6 levels... from C:/InstantRails/InstantRails/ruby/lib/ruby/site_ruby/1.8/rubygems/c ustom_require.rb:27:in `gem_original_require'' from C:/InstantRails/InstantRails/ruby/lib/ruby/site_ruby/1.8/rubygems/c ustom_require.rb:27:in `require'' from C:/InstantRails/InstantRails/ruby/lib/ruby/gems/1.8/gems/activesupp ort-1.3.1/lib/active_support/dependencies.rb:147:in `require'' from script/server:3 Does anybody have an idea of how i might fix this? Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Ron, Check your config/database.yaml and config/environment.rb files and make sure they exist and are configured correctly. Nate --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
They exist. I''m not really sure what i''m looking for in them, but i didn''t touch them. I''m assuming Instant Rails automatically creates the database for you. I also cannot get the sample cookbook projects to start when i click on ''start with mongrel'', the dos window closes right away. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 10/24/06, Ron <ron.bartreuse-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > They exist. I''m not really sure what i''m looking for in them, but i > didn''t touch them. I''m assuming Instant Rails automatically creates > the database for you. I also cannot get the sample cookbook projects > to start when i click on ''start with mongrel'', the dos window closes > right away.No, rails does not create the database for you. The config/database.yaml file will have default names for your development, test, and production databases, but you still have to physically create the database (and change the names if you choose a different name). To see what''s going on with Mongrel, open a Ruby console window through Instant Rails, navigate into the cookbook directory, and run the command "mongrel_rails". Now you should be ably to see why its aborting without the window going away on you. Curt --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 10/26/06, Curt Hibbs <ml.chibbs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 10/24/06, Ron <ron.bartreuse-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > They exist. I''m not really sure what i''m looking for in them, but i > > didn''t touch them. I''m assuming Instant Rails automatically creates > > the database for you. I also cannot get the sample cookbook projects > > to start when i click on ''start with mongrel'', the dos window closes > > right away. > > No, rails does not create the database for you. The > config/database.yaml file will have default names for your > development, test, and production databases, but you still have to > physically create the database (and change the names if you choose a > different name). > > To see what''s going on with Mongrel, open a Ruby console window > through Instant Rails, navigate into the cookbook directory, and run > the command "mongrel_rails". Now you should be ably to see why its > aborting without the window going away on you.Sorry, I should have said to run the command "mongrel_rails start". You can also force mongrel to do debug logging with "mongrel_rails start -B", then look for the log file in your Rails app''s "log" subdirectory. Curt --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---