Hi Dan, I had these problems too with 0.10.* and they've gone in 0.11.* (not sure which exact version though, latest is 0.11.4 and no segfaults there for me).
You still need to be careful when having multiple processes writing to the same Ferret database though (which I'm assuming you're doing here to get this error). It won't segfault any more but you could still get write lock errors. The general advice seems to be to use DRb to provide a ferret object for multiple processes (aaf has this in trunk now I believe). John. On Thu, 2007-04-19 at 10:12 -0700, dph wrote: > I've been using ferret with great results now for a while, but in the last > week, I've > been running into some issues. > > I will occasionally see this message: > > Exception Message: Lock Error occured at <except.c>:103 in xpop_context > Error occured in index.c:5368 - iw_open > Couldn't obtain write lock when opening IndexWriter > > Which is accompanied by mongrel segfaulting with this message in the logs: > > /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.13/lib/ferret/index.rb:284: > [BUG] Segmentation fault > -- http://johnleach.co.uk _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
