# Problem with acts\_as\_ferret and REE-20090421

**URL:** <https://www.ruby-forum.com/t/problem-with-acts-as-ferret-and-ree-20090421/167498>\
**Category:** Ferret\
**Created:** [May 8, 2009, 3:53pm UTC](https://www.ruby-forum.com/t/problem-with-acts-as-ferret-and-ree-20090421/167498 "2009-05-08T15:53:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/y/858c86/32.png) [@yar](https://www.ruby-forum.com/u/yar)\
**Post date:** [May 8, 2009, 3:53pm UTC](https://www.ruby-forum.com/t/problem-with-acts-as-ferret-and-ree-20090421/167498/1 "2009-05-08T15:53:32Z")

</div>

Hi

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.

## Regards

Yar

---

<div class="post-metadata">

**Author:** ![yar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/y/858c86/32.png) [@yar](https://www.ruby-forum.com/u/yar)\
**Post date:** [May 9, 2009, 3:14pm UTC](https://www.ruby-forum.com/t/problem-with-acts-as-ferret-and-ree-20090421/167498/2 "2009-05-09T15:14:44Z")

</div>

Yaroslav Dmitriev wrote:

> 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?

–  
Roderick van Domburg  
[http://www.nedforce.com](http://www.nedforce.com)

---

<div class="post-metadata">

**Author:** ![yar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/y/858c86/32.png) [@yar](https://www.ruby-forum.com/u/yar)\
**Post date:** [May 9, 2009, 11:02pm UTC](https://www.ruby-forum.com/t/problem-with-acts-as-ferret-and-ree-20090421/167498/3 "2009-05-09T23:02:02Z")

</div>

Roderick van Domburg wrote:

> 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