Did anyone ever figure out what this was about? I’m getting the same
error and I’m not entirely sure what’s wrong. It’s occurring on a
model, and the problem goes away when I comment out the Acts_As_Ferret
plugin.
Did anyone ever figure out what this was about? I’m getting the same
error and I’m not entirely sure what’s wrong. It’s occurring on a
model, and the problem goes away when I comment out the Acts_As_Ferret
plugin.
James H
I too am now seeing this problem with 1.2.3 and one of my model classes.
The problem is intermittent for me and it seems I can get rid of it by
bouncing my mongrels when it happens.
There’s an open ticket but we can’t get any closure on it. I actually
see
this in a controller on a production 1.2.3 app occasionally. It’s quite
irritating.
Perhaps if the related ticket at http://dev.rubyonrails.org/ticket/7452
gets
some more attention, this bug will too. The problem is that we don’t
get
much attention to bugs from the core unless we can show how to reproduce
the
problem, which I totally understand… but this one’s a bit difficult
to
track down or reproduce on demand.
In my case, I bounce the system and I’m good, but apps stopping really
stink.
I’m getting this error intermittently as well, but only on production
running ferret with DRB.
The index crashes and then i get “X was expected to define Y”.
Killing ferret and then restarting mongrel gets things running properly
again, but it’s a major pain.
Has anyone found a real solution to this - or is ferret not ready for a
high-traffic production env?
Cheers ,
Bryan
Brian H. wrote:
There’s an open ticket but we can’t get any closure on it. I actually
see
this in a controller on a production 1.2.3 app occasionally. It’s quite
irritating.
Perhaps if the related ticket at http://dev.rubyonrails.org/ticket/7452
gets
some more attention, this bug will too. The problem is that we don’t
get
much attention to bugs from the core unless we can show how to reproduce
the
problem, which I totally understand… but this one’s a bit difficult
to
track down or reproduce on demand.
In my case, I bounce the system and I’m good, but apps stopping really
stink.
I have edge frozen on vendor, and getting these errors logged:
Expected …/config/…/app/controllers/store_controller.rb to define
StoreController …
Has anyone seen this? Any hints to fix it?
I had the same error on my production server. It has something to do
with index files. I changed RAILS_ROOT/index directory permissions to
something writable by web server and it worked.
chmod -R 777 index but it did not solve my problem.
It’s a general ‘Something went bad when trying to load
store_controller.rb’ (and rather unhelpful).
It can be a syntax error in store_controller, a require which threw a
LoadError etc…
I’ve experienced the same, but making index/ writable by web server and
restarting ferret solved the issue. It’s definitely (in my case) related
to acts_as_ferret.
I have edge frozen on vendor, and getting these errors logged:
Expected …/config/…/app/controllers/store_controller.rb to define
StoreController …
Has anyone seen this? Any hints to fix it?
I had the same error on my production server. It has something to do
with index files. I changed RAILS_ROOT/index directory permissions to
something writable by web server and it worked.
Hi
I got into the same troubles with ferret. But I don’t manage to get it
working.
What do you mean exactly by “something writable by web server” ? I tried
a
chmod -R 777 index but it did not solve my problem.
I’ve experienced the same, but making index/ writable by web server and
restarting ferret solved the issue. It’s definitely (in my case) related
to acts_as_ferret.
Oh, and besides restarting ferret, you’ll probably have to restart
mongrel.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.