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 335272 - Beagle doesnt index my files
Beagle doesnt index my files
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.2
Other All
: Normal major
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-20 20:08 UTC by alejandro vera
Modified: 2006-04-05 18:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
log of 2.3 after indexing my system (19.63 KB, application/x-gzip)
2006-03-21 02:50 UTC, alejandro vera
Details
log with all backends activated (6.36 KB, application/x-gzip)
2006-03-21 02:51 UTC, alejandro vera
Details
beagle core dump that destroyed my index (17.91 KB, text/plain)
2006-03-21 16:13 UTC, alejandro vera
Details

Description alejandro vera 2006-03-20 20:08:44 UTC
Please describe the problem:
When i was trying to reproduce bug 335048 i noticed that my files werent being
indexed...

I am using 0.2.2.1

I used beagle-index-info to see how many files were indexed i there were about
250 files :( 

i shutdown beagled, deleted .beagle and restarted.. after hours all the indexes
were reconstructed (gaim, liferea,etc) but my files were not being indexed

now i deleted the FileSystemIndex directory and restarted beagled... now
beagle-index-info shows the following

Name: Files
Count: 1
Indexing: False

Is there a way to force files indexation? i read the faq but i didnt found smth
on beagle beyond 0.1.4

Can you help me?



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 alejandro vera 2006-03-20 22:14:14 UTC
I solved my problem.. but i dont know if beagle have a bug...

looking at beagle-status i realised that every 5 mintues a directory of my eclipse instalation was being indexed.. i move my ~/bin/eclipse to /usr/local and beagled de-indexed it.. now the index is being created right.

Sounds like a bug to you? 
Comment 2 Joe Shaw 2006-03-20 23:29:45 UTC
It is probably a bug triggered when crawling that directory.

Can you reproduce it and attach the logs from ~/.beagle/Log please?
Comment 3 alejandro vera 2006-03-20 23:49:18 UTC
I told u that it was solved.. for an hour :(

some time later the files index went to 0 and started again and stoped in 2772 files

I stoped the daemon and deleted de FileSystemIndex again and started the daemon

I am going to wait a couple of hours to have the log

two things:

1) the current log is full of this:

060320 1941063693 09161 Beagle  WARN: Caught exception in DoTaskReal
060320 1941063694 09161 Beagle  WARN:         Tag: /home/alejo/.liferea/cache/feeds/rdgjacw
060320 1941063695 09161 Beagle  WARN:     Creator:
060320 1941063696 09161 Beagle  WARN: Description:
060320 1941063697 09161 Beagle  WARN:    Priority: Delayed (0)
060320 1941063703 09161 Beagle  WARN EX: System.UriFormatException: URI scheme must start with a letter and must consist of one of alphabet, digits, '+', '-' or '.' character.
060320 1941063703 09161 Beagle  WARN EX: in <0x00e5d> System.Uri:Parse (System.String uriString)
060320 1941063703 09161 Beagle  WARN EX: in <0x00014> System.Uri:ParseUri ()
060320 1941063703 09161 Beagle  WARN EX: in <0x0000a> System.Uri:Parse ()
060320 1941063703 09161 Beagle  WARN EX: in <0x00051> System.Uri:.ctor (System.String uriString, Boolean dontEscape)
060320 1941063703 09161 Beagle  WARN EX: in <0x0000f> System.Uri:.ctor (System.String uriString)
060320 1941063703 09161 Beagle  WARN EX: in (wrapper remoting-invoke-with-check) System.Uri:.ctor (string)
060320 1941063703 09161 Beagle  WARN EX: in [0x0001b] (at /home/jose/devel/pkg-mono/build-area/beagle-0.2.2.1/beagled/LifereaQueryable/LifereaQueryable.cs:304) Beagle.Daemon.LifereaQueryable.FeedIndexableGenerator:current_itemToIndexable ()
060320 1941063703 09161 Beagle  WARN EX: in [0x0000d] (at /home/jose/devel/pkg-mono/build-area/beagle-0.2.2.1/beagled/LifereaQueryable/LifereaQueryable.cs:298) Beagle.Daemon.LifereaQueryable.FeedIndexableGenerator:GetNextIndexable ()
060320 1941063703 09161 Beagle  WARN EX: in [0x00041] (at /home/jose/devel/pkg-mono/build-area/beagle-0.2.2.1/beagled/LuceneQueryable.cs:571) Beagle.Daemon.LuceneQueryable+AddGeneratorTask:DoTaskReal ()
060320 1941063703 09161 Beagle  WARN EX: in [0x00054] (at /home/jose/devel/pkg-mono/build-area/beagle-0.2.2.1/Util/Scheduler.cs:267) Beagle.Util.Scheduler+Task:DoTask ()

The strange thing is that there is not '/home/jose' directory in my machine... neither 'jose' user !!!

2) what is 'beagle-exercise-file-system'? it doesnt have a manual and couldnt find about it in the beagle site...

Thanks again
Comment 4 alejandro vera 2006-03-21 00:24:28 UTC
two new things

I opened /home/alejo/.liferea/cache/feeds/rdgjacw and find that the <feedSource> element of it is pointing to:

|curl -s -u alejandro.vera:xxxxx https://mail.google.com/mail/feed/atom

I remeber have doing this to read my gmail account (password changed to xxxxx). I did following the instructions at the liferea website.. i think that is a problem

While i was indexing i moved the folder '/home/alejo/videos/jakarta-tomcat-5.0.28' to /home/alejo/workspace

Now in the beagle log there are 10.000 lines that says 

060320 2005263696 09161 Beagle DEBUG: Done crawling '/home/alejo/workspace/jakarta-tomcat-5.0.28/common'

if i do 

cat current-Beagle | grep -i crawl | wc -l

I obtain 10316

i am going to exclude all the jakarta tree from my indexation. I'll post how it goes...

PD: sorry for my english. it is not my mother language..
Comment 5 alejandro vera 2006-03-21 02:50:27 UTC
Created attachment 61661 [details]
log of 2.3 after indexing my system

A couple of hours ago 0.2.3 entered debian.

I drop all my indexes and started all over again.

first i ran beagled --deny-backend [all my backends except FileSystem]

I took a lot of time to index all the files. I attached the log here.

I looked for "tortura" looking for a song "tortura" de shakira. I find it inmidiatly

Later I shutdown bagled and started it again with all backends ativated.

Now I searched "tortura" and this was in the log

060320 2234096591 03388 Beagle DEBUG: Parsed query 'tortura' as text_query
060320 2234101284 03388 Beagle DEBUG: Couldn't find path of file with name '12.- Shakira - la tortura.mp3' and parent 'pYMWpZtAZ0maMedhRLUTiA'
060320 2234101288 03388 Beagle DEBUG: Couldn't find path of file with name '03.- Shakira - la tortura.mp3' and parent 'pYMWpZtAZ0maMedhRLUTiA'


I'll attach the second log (with all backends) in the next entry
Comment 6 alejandro vera 2006-03-21 02:51:45 UTC
Created attachment 61662 [details]
log with all backends activated

There is a lot of errors in here
Comment 7 alejandro vera 2006-03-21 16:13:48 UTC
Created attachment 61697 [details]
beagle core dump that destroyed my index

Today in the morning i found this in my log and now the file index only have 83 files... the index was totally corrupted
Comment 8 Joe Shaw 2006-04-05 18:44:12 UTC
Ok, a bunch of things going on in this bug.  I am going to close it because you are including a bunch of different issues in here, most of which have been fixed or that need to be addressed separately.

* The problem with liferea feeds was fixed by D Bera a little while ago.  I don't remember the bug number offhand.

* The problem in the most recently attached log, with the trace back involving "length" is now also fixed in CVS.

* The problem with certain files not showing up (they always seem to be files that start with numbers) is filed as bug 334055.  Please follow up on that problem there.

I think that's all of them.  If I missed one or if you see others with the latest CVS, please file *separate* bugs if the stack traces are very different.