Note that there are some explanatory texts on larger screens.

plurals
  1. POrails 3 app using rmagick starts using passenger standalone but fails using passenger through apache
    primarykey
    data
    text
    <p>I'm working on a Rails 3 app that includes rmagick and I'm able to start and run it successfully using WEBrick and Passenger Standalone. However, when I try running the app using Passenger within Apache, I get the following error:</p> <blockquote> <p>dlopen(/Users/20217633/.rvm/gems/ruby-1.9.2-p0@rails3/gems/rmagick-2.13.1/lib/RMagick2.bundle, 9): Symbol not found: __cg_jpeg_resync_to_restart Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected in: /usr/local//lib/libjpeg.8.dylib in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO - /Users/20217633/.rvm/gems/ruby-1.9.2-p0@rails3/gems/rmagick-2.13.1/lib/RMagick2.bundle</p> </blockquote> <p>Is anyone familiar with this problem?</p> <p><strong>=== UPDATE ===</strong></p> <p>Below is a copy of my httpd.conf:</p> <pre><code>SetEnv PATH /usr/bin:/usr/local/bin LoadModule passenger_module /Users/20217633/.rvm/gems/ruby-1.9.2-p0@rails3/gems/passenger-3.0.2/ext/apache2/mod_passenger.so LoadModule upload_progress_module modules/mod_upload_progress.so PassengerRoot /Users/20217633/.rvm/gems/ruby-1.9.2-p0@rails3/gems/passenger-3.0.2 PassengerRuby /Users/20217633/.rvm/wrappers/ruby-1.9.2-p0@rails3/ruby &lt;VirtualHost *:80&gt; ServerName www.domain.com DocumentRoot /Users/20217633/apps/github/project/public PassengerLogLevel 3 RackEnv development &lt;/VirtualHost&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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