Re: Beagle forgets indexes, files backend broken

2005/5/17, Joe Shaw <joeshaw novell com>:

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?

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 any
changes 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://local local/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....