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 577193 - Fatal error storing words
Fatal error storing words
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: General
0.6.92
Other Linux
: Normal critical
: ---
Assigned To: tracker-indexer
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2009-03-29 15:20 UTC by Reinout van Schouwen
Modified: 2010-05-17 13:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Reinout van Schouwen 2009-03-29 15:20:03 UTC 
Installed 0.6.92 today. The indexer seems to be entering an endless loop at some point. The log file shows lots of fatal errors (I got 6MB of log file in under five minutes!).

The error messages in the log are:
 "29 mrt 2009, 14:27:22: Tracker-Warning **: Could not store word 'img': with fatal error"

The word it can't store differs per entry.

Backtrace:

(gdb) thread apply all bt

+ Trace 213969

Thread 1 (Thread 0xb73826e0 (LWP 16992))

  • #0 __libc_realloc
    at malloc.c line 3700
  • #1 IA__g_realloc
    at gmem.c line 170
  • #2 g_string_maybe_expand
    at gstring.c line 359
  • #3 IA__g_string_insert_len
    at gstring.c line 694
  • #4 IA__g_string_append
    at gstring.c line 815
  • #5 IA__g_log_default_handler
    at gmessages.c line 916
  • #6 tracker_log_handler
    at tracker-log.c line 139
  • #7 IA__g_logv
    at gmessages.c line 474
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 indexer_update_word
    at tracker-db-index.c line 658
  • #10 index_flush_item
    at tracker-db-index.c line 814
  • #11 g_idle_dispatch
    at gmain.c line 3922
  • #12 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #13 g_main_context_iterate
    at gmain.c line 2448
  • #14 IA__g_main_loop_run
    at gmain.c line 2656
  • #15 main
    at tracker-main.c line 412 






Comment 1


Carlos Garnacho





          2009-03-30 10:05:57 UTC
        



Hi, did you try a reindex, etc? That's caused by the index file being corrupted for some reason, from that moment onwards it will fail to store any further word.

In 0.6.92 we fixed an issue which could be the cause for this, so there would be a difference if it was the first time this version was run or not (which would mean the corruption was caused by a previous version)

If the corruption was fully caused by 0.6.92, I'd put this bug in the "QDBM sucks" queue, and wait for sqlite FTS to replace the text indexing infrastructure...






Comment 2


Reinout van Schouwen





          2009-03-30 10:11:50 UTC
        



I have forced a reindex and will report if the problem happens again. However, people who upgrade from an earlier version shouldn't have to solve this problem manually.






Comment 3


Carlos Garnacho





          2009-03-30 10:38:55 UTC
        



Yeah, indeed :), but as you may understand, data storage corruption is not an expected situation, and neither should be a result from upgrading. But you're right in that we could have better mechanisms to improve interaction with the user if this happens...






Comment 4


Martyn Russell





          2009-03-30 11:40:55 UTC
        



So you are definitely using 0.6.92 and a reindex still causes these errors.

How much data are you indexing? I wonder if we are reaching some sort of limit here with the amount of words we are indexing. 

I don't suppose you know if this happens for just a particular file either do you? I wonder if some files cause problems for us. If that's true, it would be great if you could find out which file and attach it here.

To find out which file you are indexing, you will need to set the log verbosity to 3 in $HOME/.config/tracker/tracker.cfg. The filename being indexed should be in the log before all those warnings.

Any information you can give us to try and catch this bug would be very helpful.






Comment 5


Andres Mujica





          2009-04-08 02:37:04 UTC
        



Hi, this bug was linked at Launchpad to bug #346912  

https://bugs.edge.launchpad.net/ubuntu/+source/tracker/+bug/346912

In fact it seems to be an issue with QDBM.

I'm reindexing right now in order to check if a specific file is causing this.

The package used 0.6.92-1ubuntu2 at Jaunty Beta.

Thanks in advance,






Comment 6


Jürg Billeter





          2010-03-04 10:58:31 UTC
        



This should not happen anymore with 0.7 (QDBM replaced by SQLite FTS).






Comment 7


Martyn Russell





          2010-05-17 13:31:44 UTC
        



Moving "Indexer" component bugs to "General" since "Indexer" refers to the old 0.6 architecture