Re: [Tracker] error no reply within specified time



Laurent Aguerreche wrote:
Le dimanche 06 aoÃt 2006 Ã 15:35 +0100, Jamie McCracken a Ãcrit :
Gergan Penkov wrote:

I would delete ~/.Tracker/data folder and restart over. It looks like you killed with -9 trackerd at some point and damaged the DB (I take
it you are not using ext3 for your home directory?)


Hi I have had such situations, one could repair the tables with myisamchk -r -q *.MYI in .Tracker/data/mysql and .Tracker/data/tracker.
is there some way to add checks for this and REPAIR TABLE statements
somewhere on tracker's start.
we have auto repair enabled (tables that are not marked as closed are checked and then auto repaired on startup if necessary). If corruption is really bad then you might have to delete tracker's DB as the repair is not guaranteed


Out of curiosity, what's the problem with ext3 and the home directory?
its totally safe on ext3 and you should never get corruption on any file let alone tracker's db.

Hum... Sorry but I use ext3 and my database just crashed and is now
corrupted!

It ran in gdb:

(gdb) run
Starting program: /usr/bin/trackerd
[Thread debugging using libthread_db enabled]
[New Thread -1482455360 (LWP 29618)]


Tracker version 0.5.0 Copyright (c) 2005-2006 by Jamie McCracken
(jamiemcc gnome org)

This program is free software and comes without any warranty.
It is licensed under version 2 of the General Public License which can
be viewed at http://www.gnu.org/licenses/gpl.txt

Initialising tracker...
DB initialised - embedded mysql version is 50022
Checking for Options table...
Options table is present
Checking tracker DB version...Current version is 3 and needed version is
3
Creating stored procedures...
060807 20:35:40 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/mysql/proc' is marked as crashed and should
be repaired
060807 20:35:40 [Warning] Checking table:
'/home/laurent/.Tracker/data//mysql/proc'
060807 20:35:41 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/tracker/Services' is marked as crashed and
should be repaired
060807 20:35:41 [Warning] Checking table:
'/home/laurent/.Tracker/data//tracker/Services'
-----------------------
Fetching index stats...
Total files indexed : 49545
Development Files : 16692 (33.69%)
Documents : 3444 (6.95%)
Folders : 4390 (8.86%)
Images : 6524 (13.17%)
Music : 3548 (7.16%)
Other Files : 6173 (12.46%)
Text Files : 8429 (17.01%)
Videos : 345 (0.70%)
-----------------------

[New Thread -1483547728 (LWP 29625)]
[New Thread -1491940432 (LWP 29626)]
[New Thread -1500333136 (LWP 29627)]
060807 20:35:46 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed
060807 20:35:46 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed
tracker_exec_sql failed: Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed [Call PrepareQueries()]
060807 20:35:46 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed
060807 20:35:46 [ERROR] mysql_embedded: Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed
 mysql_stmt_prepare(), query failed due to Table
'/home/laurent/.Tracker/data/tracker/ServiceMetaData' is marked as
crashed and last (automatic?) repair failed

** ERROR **: file tracker-db.c: line 447 (tracker_db_prepare_queries):
assertion failed: (tracker_db_prepare_statement (db_con->db,
&db_con->insert_contents_stmt, INSERT_CONTENTS) == 3)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1491940432 (LWP 29626)]
0xffffe410 in __kernel_vsyscall ()
(gdb)

I tried to run again trackerd but my database is really corrupted.

its clear from this that it repaired the tables that tracker opens in the main thread (proc and Services table) but none of the tables that are only opened in other threads get repaired with auto-repair on. This seems like a bug but a quick fix might be to open all tables in the main thread at startup?


--
Mr Jamie McCracken
http://jamiemcc.livejournal.com/




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