Jump to content

tashman

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by tashman

  1. I have an instance of Mongrel running which is preventing me from starting my rails application. Can you kill it for me? User: tashman domain: battleship.heliohost.org Error in Mongrel Log: ** Daemonized, any open files are closed. Look at log/mongrel.pid and log/mongrel.log for info. ** Starting Mongrel listening at 0.0.0.0:12094 /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/tcphack.rb:12:in `initialize_without_backlog': Address already in use - bind(2) (Errno::EADDRINUSE) Thanks
  2. I managed to load the schema programatically using this code here at the end of my environment.rb file ActiveRecord::Schema.load("db/schema.rb") I had to go back to using the mysql gem instead of mysql2. Suffice to say the app is up and running although there are still some runtime errors, but should be able to figure them out. Thanks
  3. Think I'm finally making progress. Ended up having to change my entire boot.rb file and then followed the errors that Mongrel gave until it finally started up, but it was starting without database support. So I added in the database support and now its just telling me that it can't connect to the database most likely because the schema isn't loaded on it. /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:62:in `establish_connection': development database is not configured (ActiveRecord::AdapterNotSpecified) from /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:55:in `establish_connection' from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:438:in `initialize_database' from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:141:in `process' from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:113:in `send' from /usr/lib/ruby/gems/1.8/gems/rails-2.3.11/lib/initializer.rb:113:in `run' from /home/tashman/rails_apps/BattleShipApp/config/environment.rb:10 Can you run "rake db:schema:load" for me please.
  4. Ok I'm sorry. Cpanel really shouldn't let you upgrade gems to incompatible versions . Anyways, I've downgraded all of my gems and have replaced the require rails/all with what it does ie: require "rails" %w( active_record action_controller action_mailer active_resource rails/test_unit ).each do |framework| begin require "#{framework}" rescue LoadError end end However, it can't seem to find "rails" and mongrel gives this error: /home/tashman/rails_apps/BattleShipApp/config/application.rb:4:in `require': no such file to load -- rails (LoadError) from /home/tashman/rails_apps/BattleShipApp/config/application.rb:4 Is rails also part of Rails 3?/Is there any equivalent for rails 2? I might have to try setting up a local environment in rails 2 to see how apps start. Been using Rails 3 prerelease so I have no experience with the previous versions. Thank you for your help Geoff.
  5. Still a no go: /home/tashman/rails_apps/BattleShipApp/config/application.rb:3:in `require': no such file to load -- rails/all (LoadError) from /home/tashman/rails_apps/BattleShipApp/config/application.rb:3 I'm guessing that rails/all is suppose to be the file "all.rb" that is located in the railties gem. (located here: /home/tashman/ruby/gems/gems/railties-3.0.9/lib/rails/all.rb)
  6. Thanks. Now I'm receiving this error: /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:87:in `materialize': Could not find mysql2-0.3.6 in any of the sources (Bundler::GemNotFound) from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:81:in `map!' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:81:in `materialize' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:90:in `specs' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:135:in `specs_for' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/definition.rb:124:in `requested_specs' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/environment.rb:23:in `requested_specs' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/runtime.rb:11:in `setup' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler.rb:107:in `setup' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/setup.rb:17 from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:57:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:57:in `require' from /home/tashman/rails_apps/BattleShipApp/config/boot.rb:6 The mysql2-0.3.6 gem is clearly installed at /home/tashman/ruby/gems/gems which is where cPanel installed the gem when I used the ruby gem installer in cPanel. I have added $:.push("/home/tashman/ruby/gems") to my environment.rb is there something else that needs to be done for ruby to look at that folder for the gems? Did you happen to receive any errors while running the gem install bundler? The mysql2 gem is known to throw errors when using gem install bundler.
  7. Sure works for me as long as it fixes the issue.
  8. I'm trying to deploy my first RoR application, but I have no idea how to install the bundler so that all my gems work correctly. Usually this requires using shell with the command "gem install bundler" or just "install bundler" within the application directory that I want the gems configured for. Is there any way to set up gems manually that does not require bundler? Currently I receive this error back from Mongrel: ** Daemonized, any open files are closed. Look at log/mongrel.pid and log/mongrel.log for info. ** Starting Mongrel listening at 0.0.0.0:12094 ** Starting Rails with development environment... /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- bundler/setup (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require' from /home/tashman/rails_apps/BattleShipApp/config/boot.rb:6 Which from what I have read just means that bundler was not setup correctly as I have mentioned above.
×
×
  • Create New...