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 171516 - Lock obtain timed out error
Lock obtain timed out error
Status: RESOLVED NOTGNOME
Product: beagle
Classification: Other
Component: General
0.0.x
Other Linux
: Normal normal
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 171031 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-24 18:40 UTC by Mike Chavoustie
Modified: 2005-05-19 04:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Here's the current-Beagle log with the traces. (32.38 KB, text/plain)
2005-03-24 18:46 UTC, Mike Chavoustie 		Details
trow's requested ls log. (10.70 KB, text/plain)
2005-03-24 18:51 UTC, Mike Chavoustie 		Details
lsof | grep beagle trace. (611.17 KB, text/plain)
2005-03-24 20:11 UTC, Mike Chavoustie 		Details

Description Mike Chavoustie 2005-03-24 18:40:45 UTC 
Version details: 0.0.8+CVS
Distribution/Version: Gentoo

Seemingly randomly, beagled will "get stuck" on certain files when crawling my
filesystem.  A look at the log shows that a "Lock obtain timed out" exception is
thrown, and it prevents me from making queries using best or beagle-query.  The
log is attached.
Comment 1 Mike Chavoustie 2005-03-24 18:46:12 UTC 
Created attachment 39213 [details]
Here's the current-Beagle log with the traces.

I forgot to mention earlier my mono/etc. stack:

mono-1.1.4
dbus-0.23.4
beagle-0.0.8+CVS (CVS to allow compatiblity with inotify 0.21)
Comment 2 Mike Chavoustie 2005-03-24 18:51:30 UTC 
Created attachment 39215 [details]
trow's requested ls log.
Comment 3 Mike Chavoustie 2005-03-24 20:11:21 UTC 
Created attachment 39219 [details]
lsof | grep beagle trace.

lsof -g <PID of Beagle> didn't return anything, so I did a general lsof and
just grepped for beagle.  It lists over 5000 files.
Comment 4 Joe Shaw 2005-04-01 22:58:46 UTC 
*** Bug 171031 has been marked as a duplicate of this bug. ***
Comment 5 Joe Shaw 2005-04-05 19:30:51 UTC 
probably dup of bug 165819
Comment 6 Jon Trowbridge 2005-05-19 04:08:00 UTC 
I've heard reports that this bug can be fixed by installing mono 1.1.7 or
better, so I'm closing this as NOTGNOME.  If you are able to reproduce this with
a recent mono, please re-open the bug.