I went to look for the ferret, and as you see it is present in that location:
[EMAIL PROTECTED]:/home/44618/data/rubygems/gems/gems/ferret-0.11.6/lib$ ls ferret ferret.rb ferret_ext.so ferret_version.rb On Jun 18, 7:24 pm, Eiso <[EMAIL PROTECTED]> wrote: > I am tracking down the errors, and I think the problem has to do with > Ferret. Below is the Mongrel log file > > ** Daemonized, any open files are closed. Look at log/mongrel.pid and > log/mongrel.log for info. > ** Starting Mongrel listening at 0.0.0.0:2011 > ** Starting Rails with production environment... > /home/44618/data/rubygems/gems/gems/ferret-0.11.6/lib/ferret_ext.so: > libruby1.8.so.1.8: cannot open shared object file: No such file or > directory - /home/44618/data/rubygems/gems/gems/ferret-0.11.6/lib/ > ferret_ext.so (LoadError) > from /home/44618/data/rubygems/lib/rubygems/custom_require.rb:27:in > `require' > from /home/44618/containers/rails/socialnetwork/vendor/rails/ > activerecord/lib/../../activesupport/lib/active_support/ > dependencies.rb:496:in `require' > from /home/44618/containers/rails/socialnetwork/vendor/rails/ > activerecord/lib/../../activesupport/lib/active_support/ > dependencies.rb:342:in `new_constants_in' > from /home/44618/containers/rails/socialnetwork/vendor/rails/ > activerecord/lib/../../activesupport/lib/active_support/ > dependencies.rb:496:in `require' > from /home/44618/data/rubygems/gems/gems/ferret-0.11.6/lib/ferret.rb: > 25 > from /home/44618/data/rubygems/lib/rubygems/custom_require.rb:32:in > `gem_original_require' > from /home/44618/data/rubygems/lib/rubygems/custom_require.rb:32:in > `require' > from /home/44618/containers/rails/socialnetwork/vendor/rails/ > activerecord/lib/../../activesupport/lib/active_support/ > dependencies.rb:496:in `require' > ... 32 levels... > from /home/44618/data/rubygems/gems/gems/mongrel-1.1.5-x86-linux/ > bin/../lib/mongrel/command.rb:212:in `run' > from /home/44618/data/rubygems/gems/gems/mongrel-1.1.5-x86-linux/bin/ > mongrel_rails:281 > from /home/44618/data/rubygems/gems/bin/mongrel_rails:19:in `load' > from /home/44618/data/rubygems/gems/bin/mongrel_rails:19 > > On Jun 18, 6:57 pm, Eiso <[EMAIL PROTECTED]> wrote: > > > Hi Long, > > > Thank you very much for your help. I solved the first problem by using > > your advice but the 502 Bad Gateway error is still present. > > > I just ran script/server > > > Development.log shows: > > > [4;36;1mSQL (0.000486) [0m [0;1mSET SQL_AUTO_IS_NULL=0 [0m > > [4;35;1mPreference Load (0.000513) [0m [0mSELECT * FROM > > `preferences` LIMIT 1 [0m > > [4;36;1mAnalyzing Preference Load > > [0m [0;1mselect_type | key_len | type | id | Extra | possible_keys > > | table | rows | ref | key > > > ------------------------------------------------------------------------------------------ > > SIMPLE | | ALL | 1 | | | > > preferences | 1 | | > > [0m > > [4;35;1mPreference Columns (0.000402) [0m [0mSHOW FIELDS FROM > > `preferences` [0m > > > Production.log is empty > > > Any ideas what the above means? > > > Thank you, > > > Eiso > > > On Jun 18, 6:20 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > > > > While image_science doesn't directly require native C compilation, it uses > > > RubyInline (which does do behind-the-scenes compilations during runtime) > > > and > > > requires the FreeImage library (which would have to be built). > > > > You should uninstall the image_science gem and let your installation of > > > Insoshi use rmagick instead. It's one of MT's pre-built/installed gems > > > and > > > serves the same function (actually does a bit more than image_science but > > > we > > > currently just use it for resizing images). > > > > I believe we've taken out explicit mention of image_science in the Photos > > > model so attachment_fu should then start using rmagick automatically. If > > > not, here's a post from Michael from early on in the release of Insoshi on > > > changing from image_science to rmagick that details how to explicitly set > > > the processor (under the has_attachment in app/models/photo.rb): > > > > Hi Craig, > > > > Glad to see you got some mileage out of RailsSpace! The Insoshi code > > > base might prove useful with your image issue. We use the > > > attachment_fu plugin to handle images, instead of rolling our own as > > > we did in RailsSpace. Take a look at the Insoshi Photo model for some > > > ideas. If you do end up using the Photo data model, be sure to change > > > > :processor => 'ImageScience' > > > > to > > > > :processor => 'Rmagick' > > > > You might also want to take a look > > > athttp://clarkware.com/cgi/blosxom/2007/02/24forsomemore guidance. > > > > We started RailsSpace way before Heroku was even a glimmer in the > > > founders' eyes. If we'd know what they were going to do, we might > > > have made more of an effort to use RMagick! > > > > Cheers, > > > > Michael > > > > Search the Google group for "rmagick" as Fountain had posted up an issue > > > and > > > resolution when uploading images that you may or may not run into > > > depending > > > on some of MT's web configuration settings. > > > > As far as the Bad Gateway error you're running into, I'm not sure what the > > > issue is. Switching to rmagick may resolve it because of the exception > > > thrown with RubyInline and image_science. If you still run into this, > > > take > > > a look at log/production.log to see if there's a exception trace. > > > > Long > > > > On Wed, Jun 18, 2008 at 3:44 AM, Eiso <[EMAIL PROTECTED]> wrote: > > > > > Hi Long, > > > > > Thank you very much for your extensive answer. > > > > > I have setup an account with Media Temple, followed all the steps on > > > > their site to install Ruby. > > > > I then followed the Insoshi Install Guide, I installed the following > > > > Gems: > > > > > * rails > > > > * ferret - for search capability > > > > * image_science - if you're using FreeImage > > > > * mysql - if you're using MySQL as your database engine > > > > > I then updated my database.yml file to MySQL details (this worked out > > > > fine). > > > > > Then I executed: rake install, which also worked out. > > > > > I then executed: rake db:sample_data:reload , which executed fine up > > > > untill 26. after that the following errors came: > > > > > --- > > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 3:23: FreeImage.h: No such file or directory > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > > > Inline_ImageScience_aa58.c: In function `unload': > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 9: error: `FIBITMAP' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 9: error: (Each undeclared identifier is reported only once > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 9: error: for each function it appears in.) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 9: error: `bitmap' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 9: error: parse error before ')' token > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 11: warning: implicit declaration of function `FreeImage_Unload' > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > > > Inline_ImageScience_aa58.c: At top level: > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 17: error: parse error before '*' token > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > > > Inline_ImageScience_aa58.c: In function `wrap_and_yield': > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 18: error: `fif' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 18: error: `self' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 20: error: `image' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > > > Inline_ImageScience_aa58.c: At top level: > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 26: error: parse error before "FIBITMAP" > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > > > Inline_ImageScience_aa58.c: In function `copy_icc_profile': > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 27: error: `FREE_IMAGE_FORMAT' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 27: error: parse error before "fif" > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 28: error: `fif' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 28: error: `FIF_PNG' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 28: warning: implicit declaration of function > > > > `FreeImage_FIFSupportsICCProfiles' > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 29: error: `FIICCPROFILE' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 29: error: `profile' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 29: warning: implicit declaration of function > > > > `FreeImage_GetICCProfile' > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 29: error: `from' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 31: warning: implicit declaration of function > > > > `FreeImage_CreateICCProfile' > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/Inline_ImageScience_aa58.c: > > > > 31: error: `to' undeclared (first use in this function) > > > > /tmp/ruby.hiddendomainname.com/.ruby_inline/ > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
