Hi Dave, I am using ferret at my site http://gifthat.com and I just had a few exceptions pop up. I don''t have a way to reproduce them, but my site just was listed on lifehacker.com and these issues have popped up under multiple concurrent users (only twice though which I think isn''t too bad). I am using two lighttpd instances both with read/write access to the index: 1) Error occured at <fs_store.c>:318 Error: exception 2 not handled: Couldn''t open the file to read This happened while adding a document to the index like so: gift_index << self.to_doc 2) Error occured at <index_rw.c>:2642 Error: exception 6 not handled: Could not obtain commit lock when trying to write index This happened while doing a search_each like so: gift_index.search_each The weird thing is that I would think the search each doesn''t need to write to the index. Both of these issues appear to have happened at the same time, so they may be related to each other. Thanks for your excellent work on Ferret! Please let me know if you need any more info from me. Tom Davies http://atomgiant.com http://gifthat.com
On 8/5/06, Tom Davies <atomgiant at gmail.com> wrote:> Hi Dave, > > I am using ferret at my site http://gifthat.com and I just had a few > exceptions pop up. I don''t have a way to reproduce them, but my site > just was listed on lifehacker.com and these issues have popped up > under multiple concurrent users (only twice though which I think isn''t > too bad). I am using two lighttpd instances both with read/write > access to the index: > > 1) Error occured at <fs_store.c>:318 > Error: exception 2 not handled: Couldn''t open the file to read > > This happened while adding a document to the index like so: > > gift_index << self.to_docI''m afraid there isn''t much more I can do about this bug without more information. If you can help me reproduce it here I can usually fix it very quickly.> 2) Error occured at <index_rw.c>:2642 > Error: exception 6 not handled: Could not obtain commit lock when > trying to write index > > This happened while doing a search_each like so: > > gift_index.search_each > > The weird thing is that I would think the search each doesn''t need to > write to the index.If you are using the Index class and you call a search method on an Index object that has just written to the index then the Index object will need to commit any changes before opening the IndexSearcher. It is possible that the commit lock was still hanging around after the first crash?> Both of these issues appear to have happened at the same time, so they > may be related to each other. > > Thanks for your excellent work on Ferret! Please let me know if you > need any more info from me.Like I said earlier, if you can reproduce the error I may be able to help. Otherwise I''m fully committed to getting 0.10 out. When it is out, I''d recommend getting it into your development app as soon as you can. Although it may be a little less stable then the 0.9 series, it shouldn''t be long before it is more stable. Cheers, Dave
Thanks Dave. If I can isolate this issue I will get back to you with more information. It has happened a few more times in those exact same two places, but not enough to be a big deal for now. Thanks, Tom On 8/4/06, David Balmain <dbalmain.ml at gmail.com> wrote:> On 8/5/06, Tom Davies <atomgiant at gmail.com> wrote: > > Hi Dave, > > > > I am using ferret at my site http://gifthat.com and I just had a few > > exceptions pop up. I don''t have a way to reproduce them, but my site > > just was listed on lifehacker.com and these issues have popped up > > under multiple concurrent users (only twice though which I think isn''t > > too bad). I am using two lighttpd instances both with read/write > > access to the index: > > > > 1) Error occured at <fs_store.c>:318 > > Error: exception 2 not handled: Couldn''t open the file to read > > > > This happened while adding a document to the index like so: > > > > gift_index << self.to_doc > > I''m afraid there isn''t much more I can do about this bug without more > information. If you can help me reproduce it here I can usually fix it > very quickly. > > > 2) Error occured at <index_rw.c>:2642 > > Error: exception 6 not handled: Could not obtain commit lock when > > trying to write index > > > > This happened while doing a search_each like so: > > > > gift_index.search_each > > > > The weird thing is that I would think the search each doesn''t need to > > write to the index. > > If you are using the Index class and you call a search method on an > Index object that has just written to the index then the Index object > will need to commit any changes before opening the IndexSearcher. It > is possible that the commit lock was still hanging around after the > first crash? > > > Both of these issues appear to have happened at the same time, so they > > may be related to each other. > > > > Thanks for your excellent work on Ferret! Please let me know if you > > need any more info from me. > > Like I said earlier, if you can reproduce the error I may be able to > help. Otherwise I''m fully committed to getting 0.10 out. When it is > out, I''d recommend getting it into your development app as soon as you > can. Although it may be a little less stable then the 0.9 series, it > shouldn''t be long before it is more stable. > > Cheers, > Dave > _______________________________________________ > Ferret-talk mailing list > Ferret-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/ferret-talk >-- Tom Davies http://atomgiant.com http://gifthat.com
On 8/5/06, Tom Davies <atomgiant at gmail.com> wrote:> Thanks Dave. If I can isolate this issue I will get back to you with > more information. It has happened a few more times in those exact > same two places, but not enough to be a big deal for now.Thanks Tom. Even once is a big enough deal to be concerned as far as I''m concerned.
Yeah, I agree, it would be nice if it didn''t happen at all. One question I had for you: Is there a way to run the c version of ferret on Windows? Since I do all of my development on Windows, that would be the only real way I could try to research this one. Thanks, Tom On 8/5/06, David Balmain <dbalmain.ml at gmail.com> wrote:> On 8/5/06, Tom Davies <atomgiant at gmail.com> wrote: > > Thanks Dave. If I can isolate this issue I will get back to you with > > more information. It has happened a few more times in those exact > > same two places, but not enough to be a big deal for now. > > Thanks Tom. Even once is a big enough deal to be concerned as far as > I''m concerned. > _______________________________________________ > Ferret-talk mailing list > Ferret-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/ferret-talk >-- Tom Davies http://atomgiant.com http://gifthat.com
On 8/6/06, Tom Davies <atomgiant at gmail.com> wrote:> Yeah, I agree, it would be nice if it didn''t happen at all. > > One question I had for you: Is there a way to run the c version of > ferret on Windows? Since I do all of my development on Windows, that > would be the only real way I could try to research this one.Unfortunately no, not with the 0.9 series. Not without a fair bit of work anyway. But the 0.10 series on the other hand will be coming with a win32 gem.