Databases
StackOverflow2013
Postsdbo
PORails 2.x mongrel won't start after upgrading to rails 3. -- mongrel_rails (MissingSourceFile)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 2.x mongrel won't start after upgrading to rails 3. -- mongrel_rails (MissingSourceFile)
    primarykey
    data
    text
    <p>After upgrading my Rails install to Rails 3 on OS X, I’ve had problems running my Rails 2.x development sites with Mongrel. WEBrick seems to work, but I really would like to have the nice output of Mongrel for debugging.</p> <p>After running <code>$ script/server</code> I get this:</p> <pre class="lang-none prettyprint-override"><code>/Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:489:in `load': no such file to load -- mongrel_rails (MissingSourceFile) from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:489:in `load' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:342:in `new_constants_in' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:489:in `load' from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/commands/servers/mongrel.rb:64 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:49:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:49:in `require' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:342:in `new_constants_in' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require' from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/commands/server.rb:39 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:49:in `gem_original_require' </code></pre> <p>So far, here’s what I’ve tried:</p> <pre class="lang-none prettyprint-override"><code>$ sudo gem update system </code></pre> <pre class="lang-none prettyprint-override"><code>$ sudo gem update </code></pre> <pre class="lang-none prettyprint-override"><code>$ sudo gem uninstall mongrel </code></pre> <pre class="lang-none prettyprint-override"><code>$ sudo gem install mongrel --include-dependencies </code></pre> <pre class="lang-none prettyprint-override"><code>$ which mongrel_rails </code></pre> <p>→ <code>/usr/bin/mongrel_rails</code></p> <pre class="lang-none prettyprint-override"><code>$ mongrel_rails start </code></pre> <p>→ Success, but no stdout</p> <pre class="lang-none prettyprint-override"><code>$ which mongrel_rails </code></pre> <p>→ <code>/usr/bin/mongrel_rails</code></p> <pre class="lang-none prettyprint-override"><code>$ rails _2.0.2_ test </code></pre> <p>→ Fresh application has same problem.</p> <ul> <li>OS: OS X.6.x</li> <li>Rails: 3.0.5 (problems are with Rails 2.x apps)</li> <li><code>gem -v</code>: 1.6.1</li> <li>Mongrel: mongrel (1.1.5)</li> </ul> <p>I’ve read EVERY Google result on "-- mongrel_rails (MissingSourceFile)"; there aren’t many.</p> <p>Can anyone here tell me how to proceed in debugging this? Thanks!</p> <h3>UPDATE:</h3> <p>I’ve now tried installing older versions of the gem and specifying those in my Rails 2.x site’s <code>config/environment.rb</code> file. I’ve tried 1.1.5, 1.1.4, and 1.2.0pre.</p> <p>None of these makes the slightest bit of difference.</p> <p>Since the executable in in <code>usr/bin</code> I’m wondering if it’s a file ownership issue that got screwed up on my Rails 3 install and if one of the files isn’t getting my paths when it runs?</p> <p><code>/Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb</code> is owned by admin / root, so that should be OK, right?</p> <p>Could it be a problem with active_support!?</p> <p>Here’s the code from <code>dependencies.rb</code> that’s throwing the error:</p> <pre class="lang-ruby prettyprint-override"><code>484 class Object 485 486 alias_method :load_without_new_constant_marking, :load 487 488 def load(file, *extras) #:nodoc: 489 Dependencies.new_constants_in(Object) { super(file, *extras) } 490 rescue Exception =&gt; exception # errors from loading file 491 exception.blame_file! file 492 raise 493 end ... </code></pre> <p>This is getting a file not found error, so it’s not looking where I know the file to be… Running mongrel_rails on command line works… Which mongrel_rails shows it in <code>usr/bin</code>, So what’s the problem?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRory O'Kane
    1. USTechism
    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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails 2.x mongrel won't start after upgrading to rails 3. -- mongrel_rails (MissingSourceFile)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails 2.x mongrel won't start after upgrading to rails 3. -- mongrel_rails (MissingSourceFile)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails 2.x mongrel won't start after upgrading to rails 3. -- mongrel_rails (MissingSourceFile)
      1. USedwardsharp
      1. VTFavorite
    1. This table or related slice is empty.
 

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