After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 342351 - Crash During Crawl Creates File That Doesn't Delete
Crash During Crawl Creates File That Doesn't Delete
Status: RESOLVED DUPLICATE of bug 340542
Product: beagle
Classification: Other
Component: General
0.2.6
Other All
: Normal normal
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-05-19 14:30 UTC by David Richards
Modified: 2006-05-19 17:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Richards 2006-05-19 14:30:13 UTC 
Please describe the problem:
Warn: Exception caught while executing :Void IndexWorker()
Warn: System.IO.IOException: Lock obain timed out:
/beagle/largo/es/Locks/lucene-66957ea45e6e75683908a6f33bd00854-write.lock -- pid
 -- process exists

Once it crashed, this message came up everytime that I attempted to restart. 
You had to physically remove the file for it to continue.  The only reason I saw
this was because I was doing a hand rebuild on a certain drive.  An automated
script would never see this and would never have the ability to delete this file
to continue.

Beagle needs to cleanup after itself and always restart.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Joe Shaw 2006-05-19 17:43:03 UTC 

*** This bug has been marked as a duplicate of 340542 ***