Re: Beagle forgets indexes, files backend broken
On Thu, 2005-05-26 at 10:34 +0200, Nico Kaiser wrote: > So is there a way to avoid these dangling locks? I did not do anything > special, but every 3-4 minutes, there are dangling locks in my mail > index, so beagle deletes the index. This makes it completely > unusable... > Any news, or anything I can provide to help finding this bug? > (still Ubuntu Hoary, Mono 1.1.7, no inotify, beagle from cvs) Is this filed in bugzilla? I couldn't find it. Try this: delete your .beagle/MailIndex directly entirely, to see if that fixes the issue. If not, please attach the full logs of both beagled and the index helper for two runs: the one in which the index is created, and the one in which it says that there are dangling locks. Oh, and run with --debug. :) Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
Hi! > 05-05-17 18.13.34.04 14799 IndexH DEBUG: Found dangling locks > in /home/nico/.beagle/MailIndex/Locks> 05-05-17 18.13.34.04 14799 IndexH DEBUG:> Purging /home/nico/.beagle/MailIndexThis implies that the daemon isn't being shut down correctly. It can't ensure that the index is safe on disk so it starts over. So is there a way to avoid these dangling locks? I did not do anything special, but every 3-4 minutes, there are dangling locks in my mail index, so beagle deletes the index. This makes it completely unusable... Any news, or anything I can provide to help finding this bug? (still Ubuntu Hoary, Mono 1.1.7, no inotify, beagle from cvs) Nico. -- Nico Kaiser ::[EMAIL PROTECTED] :: http://dumm.gelaufen.de/ ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
> > This poses a good question: How are we supposed to shut down the beagled > > daemon?>> Using beagle-shutdown.And beagled does set up signal handlers, so it should shut down cleanlyif you ctrl-c or kill it. I think I Ctrl-C'd it. I did not use beagle-shutdown because beagle-index-info did not react and I thought beagle-shutdown needs a socket connection to beagled, too...-- Nico Kaiser ::[EMAIL PROTECTED] :: http://dumm.gelaufen.de/___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
On Tue, 2005-05-17 at 23:15 +0200, Tomasz Torcz wrote: > On Tue, May 17, 2005 at 08:59:48PM +, Charlie Law wrote: > > This poses a good question: How are we supposed to shut down the beagled > > daemon? > > Using beagle-shutdown. And beagled does set up signal handlers, so it should shut down cleanly if you ctrl-c or kill it. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
On Tue, May 17, 2005 at 08:59:48PM +, Charlie Law wrote: > This poses a good question: How are we supposed to shut down the beagled > daemon? Using beagle-shutdown. -- Tomasz TorczTo co nierealne - tutaj jest normalne. [EMAIL PROTECTED] Ziomale na życie mają tu patenty specjalne. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
This poses a good question: How are we supposed to shut down the beagled daemon? On Tuesday 17 May 2005 07:10 pm, Joe Shaw wrote: > > > > - - - - 8< - - - - > > 05-05-17 18.13.34.04 14799 IndexH DEBUG: Found dangling locks > > in /home/nico/.beagle/MailIndex/Locks > > 05-05-17 18.13.34.04 14799 IndexH DEBUG: > > Purging /home/nico/.beagle/MailIndex > > This implies that the daemon isn't being shut down correctly. It can't > ensure that the index is safe on disk so it starts over. How are you > shutting down the daemon? > > > BTW, I'm getting "Beagle DEBUG: Caught SocketException -- we probably > > need to launch a helper: Connection refused" every now and then when I > > try to start beagled > > That's normal debug spew... nothing to worry about. It just means that > the daemon can't connect to a helper process (because one hasn't been > spawned yet) and then launches one. > > Joe > > > ___ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
Hi, I haven't looked at the file backend log yet, but... On Tue, 2005-05-17 at 18:15 +0200, Nico Kaiser wrote: > The logfile says: > > - - - - 8< - - - - > 05-05-17 18.13.34.04 14799 IndexH DEBUG: Found dangling locks > in /home/nico/.beagle/MailIndex/Locks > 05-05-17 18.13.34.04 14799 IndexH DEBUG: > Purging /home/nico/.beagle/MailIndex This implies that the daemon isn't being shut down correctly. It can't ensure that the index is safe on disk so it starts over. How are you shutting down the daemon? > BTW, I'm getting "Beagle DEBUG: Caught SocketException -- we probably > need to launch a helper: Connection refused" every now and then when I > try to start beagled That's normal debug spew... nothing to worry about. It just means that the daemon can't connect to a helper process (because one hasn't been spawned yet) and then launches one. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
Hi!
> - The files backend indexes my files correctly, but seems to be stuck> in some directories (no special files, no special file names). It
> walks this directory over and over again even when there is no open> file at all.That's odd. Do you have write access to the directory? Are there anyerrors in the logs?
No. I'll attach the log snippet, it's repeated all the time, except the first time ("state=Dirty").
Nico.
-- Nico Kaiser ::[EMAIL PROTECTED] :: http://dumm.gelaufen.de/05-05-17 18.41.41.50 17227 Beagle DEBUG: Finished task Crawling
/home/nico/Downloads in ,14s
05-05-17 18.41.41.50 17227 Beagle DEBUG: Starting task File System Crawler
05-05-17 18.41.41.50 17227 Beagle DEBUG: Crawl Task Scheduling
/home/nico/Downloads (state=PossiblyClean)
05-05-17 18.41.41.51 17227 Beagle DEBUG: Looking at software in
/home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: Looking at Europe Live in
/home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: Looking at Mercedes-Benz_Mixed_Tape_07
in /home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: Looking at From Flickr in
/home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: Looking at fun in /home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: Finished task File System Crawler in
,00s
05-05-17 18.41.41.51 17227 Beagle DEBUG: Starting task Crawling
/home/nico/Downloads
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/.noindex?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/.noindex
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/dummy.jpg?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/dummy.jpg
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/output.avi?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/output.avi
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/iTunesSetup.exe?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/iTunesSetup.exe
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/button.xcf?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/button.xcf
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/PitchBoards2_Web2.mov?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/PitchBoards2_Web2.mov
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/IKONOS Muenchen.jpg?
05-05-17 18.41.41.51 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/IKONOS Muenchen.jpg
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/8-EarlyStoredProgramComputersadditions.ppt?
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/8-EarlyStoredProgramComputersadditions.ppt
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/diveintogreasemonkey-pdf-2005-05-09.zip?
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/diveintogreasemonkey-pdf-2005-05-09.zip
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads?
05-05-17 18.41.41.52 17227 Beagle DEBUG: *** Doing nothing to
/home/nico/Downloads
05-05-17 18.41.41.52 17227 Beagle DEBUG: Sending request!
05-05-17 18.41.41.52 17227 Beagle DEBUG: Sending message
05-05-17 18.41.41.62 17227 Beagle DEBUG: Read 269 bytes
05-05-17 18.41.41.63 17227 Beagle DEBUG: Read 1 bytes
05-05-17 18.41.41.64 17227 Beagle DEBUG: Got reply
05-05-17 18.41.41.64 17227 Beagle DEBUG: Closed client
05-05-17 18.41.41.64 17227 Beagle DEBUG: Done sending request
05-05-17 18.41.41.64 17227 Beagle DEBUG: Got response!
05-05-17 18.41.41.64 17227 Beagle DEBUG: Finished task Crawling
/home/nico/Downloads in ,13s
05-05-17 18.41.41.65 17227 Beagle DEBUG: Starting task File System Crawler
05-05-17 18.41.41.65 17227 Beagle DEBUG: Crawl Task Scheduling
/home/nico/Downloads (state=PossiblyClean)
05-05-17 18.41.41.65 17227 Beagle DEBUG: Looking at software in
/home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: Looking at Europe Live in
/home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: Looking at Mercedes-Benz_Mixed_Tape_07
in /home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: Looking at From Flickr in
/home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: Looking at fun in /home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: Finished task File System Crawler in
,00s
05-05-17 18.41.41.65 17227 Beagle DEBUG: Starting task Crawling
/home/nico/Downloads
05-05-17 18.41.41.65 17227 Beagle DEBUG: *** What should we do with
/home/nico/Downloads/.noindex?
05-05-17 18.41.41.65 17227 Beagle DEBUG: *** Ignoring
/home/nico/Downloads/.noindex
05-05-17 18.41.41.65 17227 Beagle DEBUG: ***
Re: Beagle forgets indexes, files backend broken
Hi!2005/5/17, Joe Shaw <[EMAIL PROTECTED]>: On Tue, 2005-05-17 at 11:21 +0200, Nico Kaiser wrote:> - The files backend indexes my files correctly, but seems to be stuck> in some directories (no special files, no special file names). It> walks this directory over and over again even when there is no open > file at all.That's odd. Do you have write access to the directory? Are there anyerrors in the logs? I'll check for error messages later. But if I remember correctly, there were none, just crawling one single directory over and over again. chmod'ing it to 111 makes Beagle proceed to other directories. This happened to two specific directories and will happen again if I delete the index. Maybe my extended attributes are broken? Beagle has to recrawl the mail files to make sure there haven't been anychanges since it last checked. It's probably just crawling the mail files, not reindexing them. However beagle-index-info displays the count of indexed mails, and this count starts at 0 again after some time. The logfile says: - - - - 8< - - - - ... 05-05-17 18.13.33.91 14799 IndexH DEBUG: + email://[EMAIL PROTECTED]/Archive/2001/friends;uid=18 05-05-17 18.13.33.95 14799 IndexH DEBUG: Lucene Add: ,17s 10 60,008161109911 05-05-17 18.13.33.96 14799 IndexH DEBUG: worker removed: name=HandleConnection (91) 05-05-17 18.13.34.03 14799 IndexH DEBUG: worker added: name=HandleConnection (92) refcount=1 05-05-17 18.13.34.04 14799 IndexH DEBUG: Found dangling locks in /home/nico/.beagle/MailIndex/Locks 05-05-17 18.13.34.04 14799 IndexH DEBUG: Purging /home/nico/.beagle/MailIndex 05-05-17 18.13.34.08 14799 IndexH DEBUG: Flushing... ... - - - - 8< - - - - BTW, I'm getting "Beagle DEBUG: Caught SocketException -- we probably need to launch a helper: Connection refused" every now and then when I try to start beagled Nico. -- Nico Kaiser ::[EMAIL PROTECTED] :: http://dumm.gelaufen.de/___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle forgets indexes, files backend broken
On Tue, 2005-05-17 at 11:21 +0200, Nico Kaiser wrote: > - The files backend indexes my files correctly, but seems to be stuck > in some directories (no special files, no special file names). It > walks this directory over and over again even when there is no open > file at all. That's odd. Do you have write access to the directory? Are there any errors in the logs? > - When I disable the files backend, all other elements are indexed > correctly and Beagle works quite nice. However when I quit and restart > beagled, it randomly forgets indexes and re-indexes e.g. all my mail > (which is a pain for 40.000 mails). Beagle has to recrawl the mail files to make sure there haven't been any changes since it last checked. It's probably just crawling the mail files, not reindexing them. Unfortunately Evolution's data files makes this an expensive operation, which is something they are fixing for 2.4 I believe. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
