Apparently script/ferret_server (with ruby enterprise edition) silently
crashes upon the first attempt to connect to it. Nothing is written to
the log files, no messages, nothing. Must be something with DRb. I wish
there was a way to prevent its daemonization in debug mode.
Found a workaround by running script/ferret_server with standard ruby
1.8.6 (2007-09-24 patchlevel 111) [i686-linux], while the web
application remains on ruby 1.8.6 (2008-08-11 patchlevel 287)
[i686-linux] Ruby Enterprise Edition 20090421.
I am using acts_as_ferret (0.4.3) and ferret (0.11.6). Rails 2.3.2.
CentOS 5.3 32bit.
Will post a ticket to acts_as_ferret tracker when my account is approved
there by the moderator.
Apparently script/ferret_server (with ruby enterprise edition) silently
crashes upon the first attempt to connect to it. Nothing is written to
the log files, no messages, nothing. Must be something with DRb. I wish
there was a way to prevent its daemonization in debug mode.
Found a workaround by running script/ferret_server with standard ruby
1.8.6 (2007-09-24 patchlevel 111) [i686-linux], while the web
application remains on ruby 1.8.6 (2008-08-11 patchlevel 287)
[i686-linux] Ruby Enterprise Edition 20090421.
I am using acts_as_ferret (0.4.3) and ferret (0.11.6). Rails 2.3.2.
CentOS 5.3 32bit.
That’s strange. We’re not experiencing that issue with:
acts_as_ferret 0.4.3
Ferret 0.11.6
Rails 2.0.5 / 2.1.2
CentOS 5.2 x86_64
Notice the tiny differences in Rails and CentOS makes.
Have you tried recompiling the Ferret gem?
Notice the tiny differences in Rails and CentOS makes.
Have you tried recompiling the Ferret gem?
Unfortunately I cannot check a 64 bit library on a 32 bit OS. Sure, I
recompiled both gems several times. However, it is probably not ferret
itself, but DRb inside acts_as_ferret, because it works well in
development mode without standalone search server.
Regards
Yar
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.