# Expected ... to define ... errors after restart

**URL:** <https://www.ruby-forum.com/t/expected-to-define-errors-after-restart/114097>\
**Category:** Rails\
**Created:** [September 7, 2007, 9:08pm UTC](https://www.ruby-forum.com/t/expected-to-define-errors-after-restart/114097 "2007-09-07T21:08:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JN\_Coward](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e99b99/32.png) [@JN\_Coward](https://www.ruby-forum.com/u/JN_Coward)\
**Post date:** [September 7, 2007, 9:08pm UTC](https://www.ruby-forum.com/t/expected-to-define-errors-after-restart/114097/1 "2007-09-07T21:08:37Z")

</div>

Hey there,

I rebooted my server after a power outage and cannot get my site to  
work again. I am getting a lot of errors like:

Expected /home/jonas/rails/td/current/config/…/app/models/post.rb to  
define Post

and similar. The weird thing is that I changed nothing about the app.  
It just refuses to work. I redployed the app (capistrano, restarted  
the mongrel cluster, rebooted the server, nothing helps. Initially I  
suspected acts\_as\_ferret, I have seen similar errors caused by aaf  
before. I tried restarting the DRb process, then I tried removing all  
calls to acts\_as\_ferret, still, same errors.

This is a major pain, since my application has been offline for a day,  
and I have no idea what even to try. Any help would be greatly  
appreciated!

/Jonas

---

<div class="post-metadata">

**Author:** ![JN\_Coward](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e99b99/32.png) [@JN\_Coward](https://www.ruby-forum.com/u/JN_Coward)\
**Post date:** [September 8, 2007, 5:13am UTC](https://www.ruby-forum.com/t/expected-to-define-errors-after-restart/114097/2 "2007-09-08T05:13:20Z")

</div>

JN\_Coward wrote:

> the mongrel cluster, rebooted the server, nothing helps. Initially I  
> suspected acts\_as\_ferret, I have seen similar errors caused by aaf  
> before. I tried restarting the DRb process, then I tried removing all  
> calls to acts\_as\_ferret, still, same errors.
> 
> This is a major pain, since my application has been offline for a day,  
> and I have no idea what even to try. Any help would be greatly  
> appreciated!

It does look a Ferret/DRb related problem as seen here:

[http://www.ruby-forum.com/topic/77708](http://www.ruby-forum.com/topic/77708)

Restarting for the affected people in the above topic worked, so I’m not  
sure why it isn’t for you.

–  
Michael W.