When I run bundle install from the command line I get the following
below
installed in my project directory under sqlite3--with-sqlite3lib Folder.
Fetching source index for http://rubygems.org/
Installing rake (0.8.7)
Installing abstract (1.0.0)
Installing activesupport (3.0.3)
Installing builder (2.1.2)
Installing i18n (0.5.0)
Installing activemodel (3.0.3)
Installing erubis (2.6.6)
Installing rack (1.2.1)
Installing rack-mount (0.6.13)
Installing rack-test (0.5.7)
Installing tzinfo (0.3.24)
Installing actionpack (3.0.3)
Installing mime-types (1.16)
Installing polyglot (0.3.1)
Installing treetop (1.4.9)
Installing mail (2.2.14)
Installing actionmailer (3.0.3)
Installing arel (2.0.7)
Installing activerecord (3.0.3)
Installing activeresource (3.0.3)
Using bundler (1.0.7)
Installing thor (0.14.6)
Installing railties (3.0.3)
Installing rails (3.0.3)
Installing sqlite3 (1.3.3) with native extensions
Installing sqlite3-ruby (1.3.3)
Your bundle is complete! It was installed into
./sqlite3--with-sqlite3lib
When I try running dbconsole I get
Users/musdev/project_manager/sqlite3--with-sqlite3lib/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands/dbconsole.rb:94:in
`exec': Permission denied - /usr/lib/sqlite3 (Errno::EACCES)
from
/Users/musdev/project_manager/sqlite3--with-sqlite3lib/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands/dbconsole.rb:94:in
`start'
from
/Users/musdev/project_manager/sqlite3--with-sqlite3lib/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands/dbconsole.rb:9:in
`start'
from
/Users/musdev/project_manager/sqlite3--with-sqlite3lib/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands.rb:36:in
`<top (required)>'
from script/rails:6:in `require'
from script/rails:6:in `<main>'
The error said you can't read /usr/lib/sqlite3. Please ensure you have
permission to read that file/folder.
You appear to be running a mac, so you might be able to use the repair
permissions function in disk utility.
Luke
Hey Luke,
I tried repairing permissions via disk utility but was unsuccessful, I
also
ran chmod -R 0777 /usr/lib/sqlite3 in the command line and it spits out
the same error message.
I tried repairing permissions via disk utility but was unsuccessful, I
also
ran chmod -R 0777 /usr/lib/sqlite3 in the command line and it spits out
the same error message.
Put sudo before your command. If you don't have permission to read,
you'll almost certainly not have permission to write.
Luke
Now when I run sudo rails db I get
sudo rails db
/Users/musdev/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems.rb:762:in
`report_activate_error': Could not find RubyGem rails (>= 0)
(Gem::LoadError)
from
/Users/musdev/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems.rb:219:in
`activate'
from
/Users/musdev/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/rubygems.rb:1065:in
`gem'
from /Users/musdev/.rvm/gems/ruby-1.9.2-p136/bin/rails:18:in `<main>'
I tried repairing permissions via disk utility but was unsuccessful, I
also
ran chmod -R 0777 /usr/lib/sqlite3 in the command line and it spits out
the same error message.
Put sudo before your command. If you don't have permission to read,
you'll almost certainly not have permission to write.
Luke
Now when I run sudo rails db I get
I suspect he meant sudo on the chmod command, then you should not need
it on the rails command.
I suspect he meant sudo on the chmod command, then you should not need
it on the rails command.
Colin
Thanks Colin, this is what I meant:
sudo chmod -R 0777 /usr/lib/sqlite3
Tried this also Luke and still getting the same permission denied error
messageon /usr/lib/sqlite3 when I run rails dbconsole.
This is kind of wierd, I wonder why sudo chmod -R 0777 /usr/lib/sqlite3
didnt work!!!
So what you really need to do is go to where that symlink points to and
do your chmoding there.
The output of the following command will should the real location of
sqlite3
ls -l /usr/lib/sqlite3
-or-
ls -l /usr/lib | grep sqlite3
Luke
This is a pain in the arss. I ran the command ls -l /usr/lib/sqlite3 and
it spit out
total 4960
-rwxrwxrwx 1 root wheel 2534656 Mar 6 2009 libtclsqlite3.dylib
-rwxrwxrwx 1 root wheel 89 Dec 9 2007 pkgIndex.tcl
Also ran ls -l /usr/lib | grep sqlite3
-rwxr-xr-x 1 root wheel 2436160 Mar 6 2009 libsqlite3.0.dylib
lrwxr-xr-x 1 root wheel 18 Aug 30 2008 libsqlite3.dylib ->
libsqlite3.0.dylib
drwxrwxrwx 4 root wheel 136 May 27 2009 sqlite3
So i ran the sudo chmod -R 777 on each file, and still had no success
running rails db.
Do you think I should reinstall sqlite3, just guessing
I ran the command ls -l /usr/lib/sqlite3 and
it spit out
total 4960
-rwxrwxrwx 1 root wheel 2534656 Mar 6 2009 libtclsqlite3.dylib
-rwxrwxrwx 1 root wheel 89 Dec 9 2007 pkgIndex.tcl
Also ran ls -l /usr/lib | grep sqlite3
-rwxr-xr-x 1 root wheel 2436160 Mar 6 2009 libsqlite3.0.dylib
lrwxr-xr-x 1 root wheel 18 Aug 30 2008 libsqlite3.dylib ->
libsqlite3.0.dylib
drwxrwxrwx 4 root wheel 136 May 27 2009 sqlite3
So i ran the sudo chmod -R 777 on each file, and still had no success
running rails db.
Do you think I should reinstall sqlite3, just guessing
OK, you would definitely have access to the directory that is in the error message:
I have a few additional suggestions:
-make a new rails project and see if you have this same issue
-send the output of your path environment variable eg. echo $PATH
-send the contents of your database.yml
-send the output of: whereis sqlite3
-run the command at the full path of the output of the above command
-run: sqlite3
The above should give us a better indication of where the problem is happening. I don't see this as a rails issue, but something in your dev environment, so reinstalling sqlite3 could have the desired effect.
I have a few additional suggestions:
-make a new rails project and see if you have this same issue
-send the output of your path environment variable eg. echo $PATH
-send the contents of your database.yml
-send the output of: whereis sqlite3
-run the command at the full path of the output of the above command
-run: sqlite3
The above should give us a better indication of where the problem is
happening. I don't see this as a rails issue, but something in your dev
environment, so reinstalling sqlite3 could have the desired effect.
Luke
Sorry for just getting back, super busy.
So i created a new project and still Im running into the same issue.
This is in my echo $PATH:
/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/musdev/.rvm/gems/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/gems/ruby-1.9.2-p136@global/bin:/Users/musdev/.rvm/rubies/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/bin:/Users/musdev/.vim/bin:/Users/musdev/.gem/ruby/1.8/bin:/Users/musdev/.gem/ruby/1.9/bin:/usr/local/bin/:/usr/local/sbin:/usr/local/mysql/bin:/usr/lib:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin
My database.yml file contains:
# SQLite version 3.x
# gem install sqlite3-ruby (not necessary on OS X Leopard)
development:
adapter: sqlite3
database: db/development.sqlite3
pool: 5
timeout: 5000
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
adapter: sqlite3
database: db/test.sqlite3
pool: 5
timeout: 5000
So i created a new project and still Im running into the same issue.
This is in my echo $PATH:
/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/musdev/.rvm/ge ms/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/gems/ruby-1.9.2-p136@global/bin:/ Users/musdev/.rvm/rubies/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/bin:/Users/ musdev/.vim/bin:/Users/musdev/.gem/ruby/1.8/bin:/Users/musdev/.gem/ruby/1.9 /bin:/usr/local/bin/:/usr/local/sbin:/usr/local/mysql/bin:/usr/lib:/opt/loc al/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X1 1/bin:/usr/local/git/bin
Why is /usr/lib on your path? From previous messages there's an
sqlite3 file in there with it's execute permission set to true. Since
it's ahead of usr/bin, the shell is finding /usr/lib/sqlite3 and
trying to execute that, which presumably doesn't work because it's not
an executable.
