similar to: Nasty looking warnings on Debian Etch AMD64 bit box

I''m still having some crashes on my server that don''t seem to happen on my development system. One difference between them is that the server is running in 64bit mode. Are there any issues running ferret on a 64bit system? I''ve seen some old traffic on the subject but all from about 9 months ago. There are some warnings printed out when I install ferret on the

*Hi guys.. i got this type of error when i configured Gemfile then what to do?* gem "thinking-sphinx" gem ''ferret'' Updating git://github.com/mark-moseley/linecache Fetching gem metadata from https://rubygems.org/....... Fetching gem metadata from https://rubygems.org/.. Resolving dependencies... Using rake (10.0.3) Using ClothRed (0.4.1) Using RedCloth (4.2.9)

*Hi guys.. i got this type of error when i configured Gemfile then what to do?* gem "thinking-sphinx" gem ''ferret'' Updating git://github.com/mark-moseley/linecache Fetching gem metadata from https://rubygems.org/....... Fetching gem metadata from https://rubygems.org/.. Resolving dependencies... Using rake (10.0.3) Using ClothRed (0.4.1) Using RedCloth (4.2.9)

I am trying to test drive ferret on a ubuntu dapper installation. I have a ferret-test.rb file like: ----begin--------- require ''ferret'' include Ferret index = Index::Index.new(:path => ''/opt/search-index'') ----end----------- When i issue: ruby ferret-test.rb, I get: ferret-test.rb:1:in `require'': no such file to load -- ferret (LoadError)

I have 0.11.3 installed When I try 0.11.6 or 0.11.5 I get the following output Building native extensions. This could take a while... ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install ferret creating Makefile make gcc -I. -I/usr/local/lib/ruby/1.8/i686-darwin8.10.3

I noticed that indexing seemed a little slow, so I tried reinstalling the 0.9.1 gem and noticed some errors while it was building the native extensions. Ferret still works with the pure ruby versions, but I''d love to take advantage of the c speed. I''m not real familiar with C, so I was wondering if anyone know what the errors are and if they can be fixed. Thanks -Lee ******

I''ve tried 0.11.4, and it has not yet crashed, even after I removed (most of) the workarounds. However, the same is also true of 0.11.3... I haven''t seen any of these crashes for several days, which is a very good thing. I can''t remember all the workarounds I did to sidestep the crashing; some of them I don''t want to reverse because they actually were also

Hi, we are using ferret and acts_as_ferret in a single server setup. We have 2 models that use acts_as_ferret. We are running into problems where a create or update of the models cause a ferret error Ferret::FileNotFoundError occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input Where the file that needs to be opened isn''t there. The error

We have still having problems with Ferret dying on us regularly with the error message: >> ferret server error IO Error occured at <except.c>:93 in xraiseError occured in fs_store.c:127 - fs_each doing ''each'' in /var/www/web1/oms/current/script/../config/../index/production/band/20070805130005: <Too many open files> << We are running Ferret as a

Hi, I saw someone else have this earlier. The recommendation is still to downgrade to 0.11.3? Oct 01 19:56:09 ey01-s00116 rails[3175]: Ferret::FileNotFoundError (File Not Found Error occured at <except.c>:117 in xpop_contextError occured in fs_store .c:329 - fs_open_input tried to open "/data/zendesk/current/config/../index/production/ticket/_l.cfs" but it

Hi all, I upgraded from Ferret 0.11.3 to Ferret 0.11.4 because I was getting intermittent segfaults that seemed to be due to a bug which was fixed (changeset 749). Unfortunately, 0.11.4 + acts_as_ferret seems to be a bad combination. I''m getting the some "fs_store/File Not Found Error occured at <except.c>:117" which was reported in the "Constant 0.11.4

Hi, I noticed a 0.11.3 release and gave it a whirl. I''ve so far not been able to reproduce any segfaults with my ferret_killer[1] script, though I do get some errors. when the searching process is running and I start the indexing process, I immediately get: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `latest?'': File Not Found Error occured at

Folks, Since upgrading to ferret 0.11.4 on Mac OS X Tiger, I''ve been running into constant crashes when running my Rails tests. Here''s an example of the output. -- snip -- 1) Error: test_published_blog_can_be_ferreted(BlogTest): Ferret::FileNotFoundError: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input

I''m switching all my fulltext searching over to ferret using the acts_as_ferret plugin on windows (for development, will be deployed on linux). In my tests I have a setup method as follows to ensure the index is reset for each test: def setup Item.rebuild_index end This works fine for the initial few tests but then suddenly fails for the last few tests when it seems to be

I''m switching all my fulltext searching over to ferret using the acts_as_ferret plugin on windows (for development, will be deployed on linux). In my tests I have a setup method as follows to ensure the index is reset for each test: def setup Item.rebuild_index end This works fine for the initial few tests but then suddenly fails for the last few tests when it seems to be failing

Hi dave, and everyone ;) I''ve finished my extension to export Index.search(..) loaded results into json. Here''s a little benchmark of what i''ve done : >> Benchmark.realtime { INDEX.search(query, :limit => 1000).hits.each { |x| INDEX[x.doc].load.to_json } } => 7.38711595535278 >> Benchmark.realtime { INDEX.search(''type:hardware'',

Full_Name: Jose Gaetan Pierre Version: 2.4.1 OS: Fedora Core 6 Submission from: (NULL) (196.27.87.14) I have been using R from within rpy for a while because I am more familiar with Python syntax. I first noticed this bug with R-2.4.0. Screendump: ------------------------------ >>> from rpy import * >>> beer = r.scan() 1: 3 4 1 1 3 4 3 3 1 3 2 1 2 1 2 3 2 3 1 1 1 1 4 3 1 26:

I am using Ferret for a Rails app in which Rails runs as one user but I have other processes that run as a different user that modify the ferret index. This is done in large part to mitigate the damage if a major exploit is found in Rails again. The problem is Ferret creates all its index files with rw for the user only. I have included a small patch that changes Ferret to create these

Hi, I''m using acts_as_ferret in with a mongrel and I'' m getting locking errors that after a while result in a corrupt database. I know about the problem with different processes writing to the index but I haven''t been able to get the DRB server working properly yet. I read on this list that another solution is to set :auto_flush to true but I''m not

Hi, would anyone have any advices on the next? I allow users to upload images to my app. I''m using attachment_fu and MiniMagick. There''s two things that I''d like to do: 1- No matter what format the original file is I''d like to save it in jgp format. 2- I want to keep all images limited to say 1000px width, so resize if they are bigger. Is there a way to do