Re: [Tracker] "Could not store word" => blocking indexing



laurent aguerreche free fr wrote:
Hi!

Hi :)

I still see tracker-indexer getting stuck with words it cannot index.
My computer has around 300 pdf where most of them have more than 8 pages written
in two columns.

Is this too many words "from all files indexed" or "from a particular file"? I am guessing the former.


If tracker-indexer cannot index these words because it has reached limit of
words then it should ignore them more quickly.


Laurent.


Selon Laurent Aguerreche <laurent aguerreche free fr>:

Hi (again)!


I looked at the tracker-applet and I saw that the number of indexed
files was not updated.
So I ran tracker with a high verbose level and I saw many times the
following line: "Could not store word 'a_word': with fatal error".

If I interrupt tracker-indexer in gdb, I obtain the following trace:

^C
Program received signal SIGINT, Interrupt.
0x0000003af80d7655 in _xstat () from /lib64/libc.so.6
(gdb) bt
#0  0x0000003af80d7655 in _xstat () from /lib64/libc.so.6
#1  0x0000003af80999a6 in __tzfile_read () from /lib64/libc.so.6
#2  0x0000003af8098cd8 in tzset_internal () from /lib64/libc.so.6
#3  0x0000003af8098ed7 in __tz_convert () from /lib64/libc.so.6
#4  0x000000000085857a in log_output (domain=0x6354bb "Tracker",
log_level=G_LOG_LEVEL_WARNING, message=0x2f4aee0 "Could not store word
'pres': with fatal error") at tracker-log.c:78
#5  0x000000000085845d in tracker_log_handler (domain=0x6354bb
"Tracker", log_level=G_LOG_LEVEL_WARNING, message=0x2f4aee0 "Could not
store word 'pres': with fatal error", user_data=0x0) at
tracker-log.c:136
#6  0x000000362a6415ab in g_logv () from /lib64/libglib-2.0.so.0
#7  0x000000362a641943 in g_log () from /lib64/libglib-2.0.so.0
#8  0x0000000000623b47 in indexer_update_word (word=0x262dd20 "pres",
new_hits=0x2620b00, indez=0x30c3500) at tracker-db-index.c:658
#9  0x0000000000623fd9 in index_flush_item (user_data=0x2572c60) at
tracker-db-index.c:814
#10 0x000000362a63779b in g_main_context_dispatch ()
from /lib64/libglib-2.0.so.0
#11 0x000000362a63af6d in ?? () from /lib64/libglib-2.0.so.0
#12 0x000000362a63b49d in g_main_loop_run ()
from /lib64/libglib-2.0.so.0
#13 0x0000000000410510 in main (argc=1, argv=0x7fff1057b7a8) at
tracker-main.c:412
(gdb)


We have been seeing this increasingly. I wonder if this is a hard limitation we are facing with QDBM and if there is no way round it other than to have multiple indexes.

Bring on FTS I say.

--
Regards,
Martyn



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]