Re: [Tracker] tracker not finishing reindex in latest git source on jaunty

[Thomas Mittelstaedt <tmstaedt t-mittelstaedt de>]

Just grabbed version 0.6.94, built and installed it, ran
tracker-processes -r and the indexing ran through okay.
Then I built nautilus with

sudo apt-get build-dep nautilus
sudo apt-get source -b nautilus

installed the resulting debian packages - and voila - the tags property
pages were back!!
Then I retrieved my tags from a backed-up version of file-meta.db via:
SELECT  s.id,  kw.MetaDataID, kw.MetaDataValue FROM Services s,
ServiceKeywordMetaData kw where MetaDataID = 19 and s.ID = kw.ServiceID

and imported it back into the current file-meta.db from a csv-file and
finally did:
INSERT INTO ServiceKeywordMetaData (ServiceID, MetaDataID,
MetaDataValue) select s.ID, ex.MetaID, ex.TAG from Services s,
tags_export ex where s.Path=ex.Path and s.Name=ex.Name

Tags were all there, so I assume, the procedure was okay.

Am Sonntag, den 03.05.2009, 23:16 +0200 schrieb Thomas Mittelstaedt:
> Am Freitag, den 01.05.2009, 11:35 +0100 schrieb Martyn Russell:
> > On Fri, 2009-05-01 at 06:43 +0200, Thomas Mittelstaedt wrote:
> > > Hallo, tracker experts,
> >
> > Hi :)
> >
> > > I just upgraded from ubuntu intrepid to jaunty and also fetched the
> > > latest git source of tracker. Unfortunately, the indexing is never
> > > finished but appears to block the dbus since other apps did hang with a
> > > certain action, which continued as normal as soon as I killed all
> > > tracker processes.
> >
> > Just so we are sure, when you say the latest version, you mean master
> > right? i.e. 0.7 branch.
>
> Yes, I fetched master.
>
> > If you already had data on your machine, I would recommend you use:
> >
> >   tracker-processes -r
> >
> > This will remove all traces of any databases, etc which will be
> > incompatible with older versions. It will also kill all tracker
> > processes.
> >
> > NOTE: The evolution push modules were recently disabled, but they may
> > STILL be installed to $prefix/lib/tracker{-0.7}/push-modules/
> >
> > If you remove that directory (the push-modules) then the indexer should
> > be a lot more responsive until we fix the issue.
> >
> > > tail -f /home/tom/.local/share/tracker/trackerd.log 
> > > 01 Mai 2009, 06:35:54: Tracker: Processed 1268/3852, indexed 0,
> > > module:'files', 01m 01s left, 29s elapsed
> > > 01 Mai 2009, 06:36:04: Tracker: <--- [3] DBus request to get daemon
> > > status
> > > 01 Mai 2009, 06:36:04: Tracker: ---> [3] Success, no error given
> > > 01 Mai 2009, 06:36:04: Tracker: Processed 1532/3852, indexed 0,
> > > module:'files', 01m left, 39s elapsed
> > > 01 Mai 2009, 06:36:14: Tracker: Processed 2404/3852, indexed 0,
> > > module:'files', 30s left, 50s elapsed
> > > 01 Mai 2009, 06:36:24: Tracker: Processed 2549/3852, indexed 0,
> > > module:'files', 30s left, 59s elapsed
> > > 01 Mai 2009, 06:36:24: Tracker: Processed 2549/3852, indexed 0,
> > > module:'files', 30s left, 59s elapsed
> > > 01 Mai 2009, 06:36:34: Tracker: Processed 3170/3852, indexed 2549,
> > > module:'files', 15s left, 01m 09s elapsed
> > > 01 Mai 2009, 06:39:19: Tracker: <--- [4] DBus request to get daemon
> > > status
> > > 01 Mai 2009, 06:39:19: Tracker: ---> [4] Success, no error given
> > > 01 Mai 2009, 06:39:36: Tracker: Statistics cache has expired,
> > > updating...
> > > 01 Mai 2009, 06:39:36: Tracker: New DBus request, pausing indexer
> > > 01 Mai 2009, 06:39:36: Tracker: State change from 'Indexing' -->
> > > 'Paused'
> > > 01 Mai 2009, 06:39:36: Tracker: Requesting statistics from database for
> > > an accurate signal
> >
> > This log doesn't look erroneous as far as I can see. You can also use
> > tracker-status -fd to follow the state changes in Tracker. Progress
> > updates (i.e. x files out of y complete) will also be available using
> > this.
> >
> > > Also, the user data backup mechanism seems to be broken again, since no
> > > ttl file was created!!
> >
> > We will investigate that, thank you for mentioning it. Also note that on
> > the 0.7 branch the TTL import code is still being migrated as far as I
> > understand. So this could well be the reason why.
> >
> > > any help appreciated!!
> >
> > Hope this helps. If you spot anything, let us know. The 0.7 branch is
> > quite new be sympathetic if you find problems :)
>
> Hmm. Maybe, I am better off grabbing one of your latest releases?!
> But thank you for the hints!!


-- 
thomas