Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to deploy an app to a fresh Ubuntu 10 installation using Passenger 2.2.15, Rails 2.3.5, Ruby 1.8.7, and Apache 2.2.14. However, even with a default rails app (sudo rails defaultapp), I am receiving the following error: "no such file to load -- initializer".

I'm not sure which files you might need copies of in order to diagnose this problem, so I'll copy a few here and hope that it will help.

Thanks for any help you can provide.



    <VirtualHost *:80>
    ServerAdmin webmaster@localhost

    DocumentRoot /var/www/appname/public
    <Directory />
        Options FollowSymLinks
        AllowOverride None
    <Directory /var/www/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride None
        Order allow,deny
        allow from all

    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
    <Directory "/usr/lib/cgi-bin">
        AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Order allow,deny
        Allow from all

    ErrorLog /var/log/apache2/error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog /var/log/apache2/access.log combined

    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from ::1/128



<IfModule passenger_module>
   PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15
   PassengerRuby /usr/bin/ruby1.8


LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/apache2/
share|improve this question

Rails was not installed into /appname/vendor/rails, I installed it by running sudo rake rails:freeze:edge RELEASE=2.3.5 and then changing permissions accordingly. It is disturbing that Ubuntu requires sudo to do everything with Rails and thus requires constant permissions manipulation.

Additionally, this resulted in another error: can't activate rack (= 1.2.1, runtime) for [], already activated rack-1.0.1 for [], which I am still working on.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.