You are not logged in.
Hey,
since a while, my beagle always crashes after a while:
Warn: Exception caught while executing Beagle.Daemon.ConnectionHandler:Void Hand leConnection()
Warn: System.IO.IOException: Lock obain timed out: /home/hunzikea/.beagle/Indexe s/FileSystemIndex/Locks/lucene-ce0379df02e535cb2140ca58b76e3a8c-write.lock -- pi d -- process exists
in [0x0010e] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/Lucene.Net/Store/Lock.cs:91) Lucene.Net.Store.Lock:Obtain (Int64 lockWaitTimeo ut)
in [0x0008d] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/Lucene.Net/Index/IndexWriter.cs:414) Lucene.Net.Index.IndexWriter:.ctor (Lucen e.Net.Store.Directory d, Lucene.Net.Analysis.Analyzer a, Boolean create, Boolean closeDir)
in [0x00005] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/Lucene.Net/Index/IndexWriter.cs:401) Lucene.Net.Index.IndexWriter:.ctor (Lucen e.Net.Store.Directory d, Lucene.Net.Analysis.Analyzer a, Boolean create)
in [0x00293] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/LuceneIndexingDriver.cs:216) Beagle.Daemon.LuceneIndexingDriver:Flush_Unlocked (Beagle.Daemon.IndexerRequest request)
in [0x0000f] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/LuceneIndexingDriver.cs:90) Beagle.Daemon.LuceneIndexingDriver:Flush (Beagle.D aemon.IndexerRequest request)
in [0x00079] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/IndexHelper/RemoteIndexerExecutor.cs:69) Beagle.IndexHelper.RemoteIndexerExecu tor:Execute (Beagle.RequestMessage raw_request)
in [0x00232] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/beagle d/Server.cs:275) Beagle.Daemon.ConnectionHandler:HandleConnection ()
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
in [0x0005a] (at /home/arjan/arch-dev/extra/gnome/beagle/src/beagle-0.2.6/Util/E xceptionHandlingThread.cs:54) Beagle.Util.ExceptionHandlingThread:ThreadStarted ()
Are the references to /home/arjan a hint to some packaging error?
This is btw on a fresh Arch install. Also, I cleaned up beagles config dir by
rm -r .beagle
Offline
Lock obain timed out: /home/hunzikea/.beagle/Indexe
Looks like deleting .beagle caused the trouble
Be yourself, because you are all that you can be
Offline
Hardly.
If one's never used beagle before there is also no .beagle directory.
I should maybe say that it doesn't crash right away, sometimes after half an hour or so. Before that, it works fine and also responds to search queries.
Offline
Are the references to /home/arjan a hint to some packaging error?
If you don't have any users named arjan, I would say yes. The maintainer's name is Arjan and beagle was recently updated. You might want to file a bug report.
A test you could do before submitting the bug, is to rebuild beagle from abs. If it works correctly after that, then it's a packaging error.
Offline
Mono applications come with debugging symbols. When you get an error, it tells you which line of the source it was, including full paths, which happens to be some build directory on the developer's system. Nothing buggy about it, though it exposes some information about the devbox the package was built on...
Offline
owh no now you know my name. :oops:
Freedom is what i love
Offline
I have the same issue, and it's in the beagle bugzilla as well (the "Sander Zwier" is me, hehe):
http://bugzilla.gnome.org/show_bug.cgi?id=340542
I will try rebuilding with ABS.
EDIT: rebuilding did not help:
060529 1342171839 17167 IndexH WARN: Exception caught while executing Beagle.Daemon.ConnectionHandler:Void HandleConnection()
060529 1342172672 17167 IndexH WARN EX: System.IO.IOException: Lock obain timed out: /home/sander/.beagle/Indexes/FileSystemIndex/Locks/lucene-448f50e04b95ddeedbfa95e3658913d4-write.lock -- pid -- process exists
060529 1342172672 17167 IndexH WARN EX: in [0x0010e] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/Lucene.Net/Store/Lock.cs:91) Lucene.Net.Store.Lock:Obtain (Int64 lockWaitTimeout)
060529 1342172672 17167 IndexH WARN EX: in [0x00039] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/Lucene.Net/Index/IndexReader.cs:547) Lucene.Net.Index.IndexReader:AquireWriteLock ()
060529 1342172672 17167 IndexH WARN EX: in [0x00014] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/Lucene.Net/Index/IndexReader.cs:576) Lucene.Net.Index.IndexReader:Delete (Int32 docNum)
060529 1342172672 17167 IndexH WARN EX: in [0x0001f] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/Lucene.Net/Index/IndexReader.cs:605) Lucene.Net.Index.IndexReader:Delete (Lucene.Net.Index.Term term)
060529 1342172672 17167 IndexH WARN EX: in [0x000a4] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/LuceneIndexingDriver.cs:126) Beagle.Daemon.LuceneIndexingDriver:Flush_Unlocked (Beagle.Daemon.IndexerRequest request)
060529 1342172672 17167 IndexH WARN EX: in [0x0000f] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/LuceneIndexingDriver.cs:90) Beagle.Daemon.LuceneIndexingDriver:Flush (Beagle.Daemon.IndexerRequest request)
060529 1342172672 17167 IndexH WARN EX: in [0x00079] (at /var/abs/extra/gnome/b
eagle/src/beagle-0.2.6/beagled/IndexHelper/RemoteIndexerExecutor.cs:69) Beagle.IndexHelper.RemoteIndexerExecutor:Execute (Beagle.RequestMessage raw_request)
060529 1342172672 17167 IndexH WARN EX: in [0x00232] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/beagled/Server.cs:275) Beagle.Daemon.ConnectionHandler:HandleConnection ()
060529 1342172672 17167 IndexH WARN EX: in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
060529 1342172672 17167 IndexH WARN EX: in [0x0005a] (at /var/abs/extra/gnome/beagle/src/beagle-0.2.6/Util/ExceptionHandlingThread.cs:54) Beagle.Util.ExceptionHandlingThread:ThreadStarted ()
Offline
http://bugzilla.gnome.org/show_bug.cgi?id=340542
So, should be fixed in CVS. I'll test it out.
EDIT: beagle-cvs is running here for about 2 hours now without showing up with that error. I take it it's fixed indeed.
Offline
Back when I tried beagle (which i'll admit was some time ago) I found it fairly unstable. I guess perhaps this hasn't changed so much...
The suggestion box only accepts patches.
Offline
Well, there is something true in what you say. Beagle has made a lot of progress, but there has never been a relese so far that I could just let run and it would do what it should. Often encountered problems were either some crashes related to the evolution bindings or abnormal memory usage followed by a crash. I really hope the guys can stabilize it and especially reduce its memory hunger somewhat, for a tool like this would really be usable, it its stable enough to be trusted on.
Offline
Yeah, esp. the enormous spikes in memory usage are a pain. As for stability, i've been running the daemon all night long (background vocal: all niiiight!) and it hasn't crashed yet.
Offline