I was trying to learn ruby on rails, so I installed the gem version 4.0.0, when I start my server, and go to localhost:8000, it brings me an error page with error message:
ActiveRecord::ConnectionNotEstablished.
I'm using sqlite3, not MySQL. Any help is appreciated.
edit: i fixed it, had to do with my database.yml
Make sure that you have installed sqlite3 gem: gem install sqlite3 or run bundle install if you have the gem listed on your Gemfile (which you should).
After that run the following commands:
rake db:create # creates the database
rake db:migrate # creates the tables based on your migration files
If the above two works fine, your application should be able to connect to the database. If not you probably have a configuration problem on your config/database.yml.
Here is my error:
rake aborted!
Gem::LoadError: You have already activated rake 10.3.1, but your Gemfile requires rake 10.2.2. Prepending `bundle exec` to your command may solve this.
/Users/AaronWilliamson/.gem/ruby/2.1.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:34:in `block in setup'
/Users/AaronWilliamson/.gem/ruby/2.1.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:19:in `setup'
/Users/AaronWilliamson/.gem/ruby/2.1.0/gems/bundler-1.5.3/lib/bundler.rb:119:in `setup'
/Users/AaronWilliamson/.gem/ruby/2.1.0/gems/bundler-1.5.3/lib/bundler/setup.rb:7:in `<top (required)>'
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/config/boot.rb:4:in `<top (required)>'
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/config/application.rb:1:in `<top (required)>'
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/Rakefile:4:in `<top (required)>'
LoadError: cannot load such file -- bundler/setup
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/config/boot.rb:4:in `<top (required)>'
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/config/application.rb:1:in `<top (required)>'
/Users/AaronWilliamson/Desktop/Ripelist-Classifieds/Rakefile:4:in `<top (required)>'
(See full trace by running task with --trace)
I can't run any rake tasks and this seems to be the root of all my other problems. It wasn't like this a couple days ago when I was running rake commands. Can anyone explain what's going on here and how to get my app back on track? I've hit a wall. Also, bundle exec doesn't fix the root of the problem for me. I never had to do that in the past and it's still not working now.
EDIT 2:
You should look at bundle update and change your workflow a little. Refer to this question for further assistance.
Original answer
This is a simple issue which happens when your gemset has a rake version that is newer than the version number your Gemfile.lock mentions.
As is mentioned in the error message, you can use bundle exec to get things working.
My solution in such cases is to just remove Gemfile.lock if I am not too worried other gem versions and their endless dependencies. Otherwise, you can try just removing the one line in Gemfile.lock which talks about the version of rake. run bundle install and the world should be a happy place again. (edit 2: Run bundle update --source instead of this. Don't do this.)
PS: Try using gemsets and organising your gems with rvm for different projects.
Edit
I prefer using rbenv now for managing installations and all gems for a project reside in vendor/bundle using bundle install --path option. Later scope every gem command with bundle exec.
Hence, rails s becomes bundle exec rails s. A little more typing is, in my opinion, better if it means that things will remain clean and conflicts such as this one don't happen.
A simple solution that worked for me is to simply run bundle update rake.
You can use rubygems-bundler to solve this. Run the following commands:
$ gem install rubygems-bundler
$ gem regenerate_binstubs
Then try your rake again.
I had a similar issue and I was skeptical about removing a line from my Gemfile.lock, it seemed hacky and the inconvenience of prepend bundle exec to every rake command was not an option either. I fixed this by first going into my Gemfile.lock to see what version of rake was there (in my case it was 11.1.2). My thought was to uninstall rake and install this version. Running gem uninstall rake gave this output:
Select gem to uninstall:
rake-10.5.0
rake-11.1.1
rake-11.1.2
rake-11.2.2
rake-11.3.0
All versions
I uninstalled both rake-11.2.2 and rake-11.3.0. That fixed my problem
Use this:
gem install rake -v "version-you-want"
My error message:
~ $ rake db:migrate [2.6.5][10:21:00]
rake aborted!
Gem::LoadError: You have already activated rake 12.3.2, but your Gemfile requires rake 13.0.1. Prepending `bundle exec` to your command may solve this.
/Users/torvalds/workspace/ekohe/whitespace/config/boot.rb:5:in `<top (required)>'
/Users/torvalds/workspace/ekohe/whitespace/config/application.rb:3:in `require_relative'
/Users/torvalds/workspace/ekohe/whitespace/config/application.rb:3:in `<top (required)>'
/Users/torvalds/workspace/ekohe/whitespace/Rakefile:6:in `require_relative'
/Users/torvalds/workspace/ekohe/whitespace/Rakefile:6:in `<top (required)>'
(See full trace by running task with --trace)
I am using the rbenv to manage my Ruby environment.
My global Ruby version is as know as the default Ruby version is 2.7.1, because I set it as rbenv global 2.7.1. However, my rake under Ruby 2.7.1 is 12.3.2
~ $ rake --version
rake, version 12.3.2
My project Ruby version is 2.6.5. however, my rake under Ruby 2.6.5 in my project is 13.0.1
~ $ bundle exec rake --version
rake, version 13.0.1
so I have to uninstall global rake
~ $ gem uninstall rake
and reinstall it back
~ $ gem install rake
Fetching rake-13.0.1.gem
Successfully installed rake-13.0.1
1 gem installed
it works! ~~~
I'm not sure whether it will have an influence on other projects. However, so far it works.
According to this solution (that worked for me) : https://stackoverflow.com/a/23668399/4260090
You can solve it by using rubygems-bundler
Type these commands in your terminal :
$ gem install rubygems-bundler
$ gem regenerate_binstubs
It should work now
Try to install nodejs, this was solved my problem.
If you're on ubuntu run this command.
sudo apt-get install nodejs
I tried another way which is delete Gemfile.lock then run bundle install. After that I run rake db:migrate. And everything works fine.
Although I don't think remove Gemfile.lock is bad practice, but may be; who know.
As mentioned on earlier answers this is a simple issue which happens when your gemset has a rake version that is newer than the version number your Gemfile.lock mentions.
The easiest way to debug this is to run bundle update.
The other ways could be to remove Gemfile.lock and running bundle install or simply deleting the line in Gemfile.lock that corresponds to the rake version and try bundle install. But this might sometimes corrupt the Gemfile. I would prefer the first method because it is the safest and the easiest.
Go in the Gemfile.lock, find the rake file and update the version there.
I got this error:
Gem::LoadError: You have already activated rake 11.2.2, but your
Gemfile requires rake 11.1.2. Prepending bundle exec to your command
may solve this.
What I did was to change the version of rake in the Gemfile.lock from:
rake (11.1.2) to rake (11.2.2).
Everything worked fine after that.
I had the same error:
You have already activated rake 12.0.0, but your Gemfile requires rake 11.3.0. Prepending "bundle exec" to your command may solve this.
I solved it by running bundle update
this updated the rake version to my activated rake version and everything worked I hope that works for you!
I meet the similar problem.
My solution is change the line of rake version "gem 'rake', '~> 10.3'" in file Gemfile, delete Gemfile.lock and run 'bundler install', the new Gemfile.lock will show the new version 10.3.1. Then everything will be fine.
I have fixed by simply prepending bundle exec as
"bundle exec rake db:create" or migrate
I experienced this issue:
Here's my solution:
Solution 1:
This solution works a lot of the time, simply update the gem causing the issue, say the gem is rack
bundle update rack
Solution 2:
In some cases Solution 1 may not work, and you will need to edit your Gemfile.lock file.
Simply, open your Gemfile.lock file and then change the version to the update requested.
In my case, the gem was rack, I had rack 2.0.7 defined in my Gemfile.lock file, but my application required rack 2.1.2, I simply had to modify it to rack 2.1.2 in the Gemfile.lock file.
I then had to uninstall the previous version of rack which is rack 2.0.7
gem uninstall rack -v 2.0.7
And finally installed the new gem in production
bundle install --without development test
Solution 3:
In very rare cases Solution 1 and Solution 2 may not work, and you will need to edit your Gemfile before updating the gem.
In my case, the gem was puma, I had puma ~> 3.11 defined in my Gemfile, but my application required puma ~> 4.3.1. At this point running bundle update puma and editing my Gemfile.lock file didn't work, since puma ~> 3.11 version specified in the Gemfile would not allow an update to puma ~> 4.3.1.
I simply had to change the version of puma in the Gemfile to puma ~> 4.3.1 and then ran the command.
bundle update puma
Solution 4:
If the version of rake that your Gemfile requires is less than the rake version activated, and you do not want to update rake, then you can as well run the command below to remove the version of rake that is activated:
gem list rake
gem uninstall rake
and then select the version of rake you want to uninstall.
That's all.
I hope this helps
I am following a ruby on rails tutorial. I have not been able to find an answer that works for this problem yet. I am on Windows 8 running Ruby 2.0 what could be causing this?
$ rake db:create
rake aborted!
cannot load such file -- sqlite3/sqlite3_native
Any possible fixes?
I was able to fix this by simply installing the latest versions on the SQLite3 and Eventmachine gems:
https://rubygems.org/gems/eventmachine
http://rubygems.org/gems/sqlite3-ruby
If you have extracted "exe"s and "dll"s from Sqlite download link to Ruby's bin folder and still have this problem. Try this:
bundle update
gem uninstall sqlite3
Given a choice between multiple versions of sqlite3, choose last option 'All versions'. Enter last number here
Select gem to uninstall:
1. sqlite3-1.3.13
2. sqlite3-1.3.13-x64-mingw32
3. All versions
>3
.
.
If you remove this gem, these dependencies will not be met.
Continue with Uninstall? [yN]
>
y
gem install sqlite3 --platform=ruby
rails db:create
This should work.
Read through this link for more explanation if above works for you.
I've just starting ruby on rails and I am still busy setting everything up running.. the problem that I encounter is that it keeps saying that mysql2 is not part of a bundle.. I have googled it obviously but the solutions didn't seem to work
sudo gem install mysql2
etc..
the stuff I get is
$ rake db:create
rake aborted!
Please install the mysql2 adapter: gem install activerecord-mysql2-adapter (mysql2 is not part of the bundle. Add it to Gemfile.)
/Library/Ruby/Gems/1.8/gems/bundler-1.3.2/lib/bundler/rubygems_integration.rb:214:in gem'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/connection_adapters/mysql2_adapter.rb:3
/Library/Ruby/Gems/1.8/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:inrequire'
/Library/Ruby/Gems/1.8/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in require'
/Library/Ruby/Gems/1.8/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:236:inload_dependency'
/Library/Ruby/Gems/1.8/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in require'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:inresolve_hash_connection'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:29:in spec'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:130:inestablish_connection'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/railties/databases.rake:90:in create_database'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/railties/databases.rake:62
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/railties/databases.rake:62:ineach'
/Library/Ruby/Gems/1.8/gems/activerecord-3.2.12/lib/active_record/railties/databases.rake:62
Tasks: TOP => db:create
(See full trace by running task with --trace)
Anyone here knows the solution for me? ( p.s. I see alot people saying that it has to be added to the gem config but how? )
You should make sure your Gemfile (located in the root of your project) includes
gem 'mysql2'
Then run the bundle install to install it.
I believe the activerecord-mysql2-adapter gem is installed as a dependency, but you can also add
gem 'activerecord-mysql2-adapter'
If it still requests it.
I'm trying to get get going on a rails tutorial and get get past the installation. I'm a newbie.
1 . ran "rails new app1." - The app is created but bundler fails (looks like it is run as part of the rails new command
An error occured while installing sqlite3 (1.3.5),
changed the gemfile to explicitly call for "gem 'sqlite3-ruby', '1.2.5', :require => 'sqlite3' (this is the most recent version that works on osx 10.5)"
ran "bundle install" - success
try to view the default app and see the error
ActiveRecord::ConnectionNotEstablished
looked in config/database.yml. It says "database: db/development.sqlite3"
looked in db/ - no database here. - - Is a db supposed to be created during rails new?
Tried running rake db:migrate - get
"rake aborted!
: Please install the sqlite3 adapter: gem install activerecord-sqlite3-adapter (sqlite3 is not part of the bundle. Add it to Gemfile.)"
Tried running that command, got
ERROR: Could not find a valid gem 'activerecord-sqlite3-adapter' (>= 0) in any repository
ERROR: Possible alternatives: activerecord-jdbcsqlite3-adapter, activerecord-sqlserver-adapter, activerecord-spatialite-adapter, activerecord-n
ulldb-adapter, activerecord-dbslayer-adapter
Anyone know what I'm missing?
Anybody have an idea what I need to do?
OSX 10.5.8 (leopard)
rails 3.2.0
ruby 1.9.2
Well that last part is a bit hairy sounding, but to get your database sorted you want:
rake db:setup
...not migration, to create the database.
rake -T | grep db
...shows you the options, for future reference. Let's see what happens after that :)