On Wed, Oct 03, 2007 at 10:08:32PM +0200, Morten wrote: > > Hi. > > We've had some problems with ferret not being able to load our classes > (stack trace below for the curious). > > I nailed it down to a deployment issue, where an old instance of ferret > drb was running. I don't understand the details quite yet, but the > result was the the old ferret was never shutdown during redeployment, > and attempts were made to start up a new one. > > Anywho, I stumbled acroess the ferret_server.log and ferret_index.log, > is it correctly understood, that ferret_server.log is basically the drb > server output, while ferret_index.log is the index manager output?
exactly. ferret_server.log is written by the DRb part of acts_as_ferret, while ferret_index.log is written by the indexing code common to local and DRb mode. > A bonus question, what's the best way to determine that your application > (using acts_as_ferret) is currently running against the drb server > rather than the file system? If your log level (set in ferret_server.yml) is on debug, ferret_server.log should have an entry for each method call received via DRb. In your application, you may check Model.aaf_configuration[:remote] to see if remote access is active. Besides that, your app should refuse to start up if it's configured for remote mode and no server is there. Cheers, Jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
