Databases
StackOverflow2013
Postsdbo
POIn Terminal: #rails works but #sudo rails does not -RVM Gemset
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIn Terminal: #rails works but #sudo rails does not -RVM Gemset
    primarykey
    data
    text
    <p><code>alec@Locke:~/workspace/rails/nwis$ rails -v Rails 3.0.7 alec@Locke:~/workspace/rails/nwis$ sudo rails -v sudo: rails: command not found</code></p> <p>I need to use sudo because I have a permission denied error when I try to run rails server on my machine.</p> <p>I think it's an issue with RVM and using Gemsets, but I don't know why. I've tried re-running the Gemset setup process using sudo for each command to make sure my root user and my regular user are on the same page, but that gave me the same result.</p> <p>To be clear as to why I am running as sudo; when trying to start a rails server, this is what happens:</p> <pre><code>rails server =&gt; Booting WEBrick =&gt; Rails 3.0.7 application starting in development on http://0.0.0.0:3000 =&gt; Call with -d to detach =&gt; Ctrl-C to shutdown server Exiting /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/rack-1.2.2/lib/rack/server.rb:267:in `initialize': Permission denied - /home/alec/workspace/rails/nwis/tmp/pids/server.pid (Errno::EACCES) from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/rack-1.2.2/lib/rack/server.rb:267:in `open' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/rack-1.2.2/lib/rack/server.rb:267:in `write_pid' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/rack-1.2.2/lib/rack/server.rb:203:in `start' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/railties-3.0.7/lib/rails/commands/server.rb:65:in `start' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/railties-3.0.7/lib/rails/commands.rb:30:in `block in &lt;top (required)&gt;' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/railties-3.0.7/lib/rails/commands.rb:27:in `tap' from /home/alec/.rvm/gems/ruby-1.9.2-p180/gems/railties-3.0.7/lib/rails/commands.rb:27:in `&lt;top (required)&gt;' from script/rails:6:in `require' from script/rails:6:in `&lt;main&gt;'` </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAlec
    1. USAlec
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIn Terminal: #rails works but #sudo rails does not -RVM Gemset
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwith rvm, you really shouldn't have to use sudo at all -- you might want to try wiping out system-wide installed gems (that you installed via sudo) and starting again. If you need the rails directory owned by another user, consider using sudo to create the necessary group, adding yourself to that group, and giving group write permission to the parent directory.
      singulars
      1. POIn Terminal: #rails works but #sudo rails does not -RVM Gemset
      1. USBen Taitelbaum
    2. COThere's a good chance that the "permission denied" error is because you've previously used sudo for something. Check the permissions of the files (especially tmp and log files), and make sure that they're owned by alec, not root. Or just try `sudo chown -R alec:users *` in the rails app directory. (use a group that exists though, like 'alec' or 'staff')
      singulars
      1. POIn Terminal: #rails works but #sudo rails does not -RVM Gemset
      1. USBen Taitelbaum
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload