|
Martyn Russell schreef op 29/10/2013
14:09:
Hi Martyn, Carlos and Brian,
Inline reply
Could you terminate it and run your own
with /usr/lib/tracker/tracker-miner-fs -v 3? That should give
some more
information about what's going on there.
Seems to have stopped with:
(tracker-miner-fs:14538): Tracker-CRITICAL **: Could not
initialize
currently active mount points:
GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal:
column
nie:url is not unique (strerror of errno (not necessarily
related): No
such file or directory)
(tracker-miner-fs:14538): Tracker-CRITICAL **: Could not set
mount point
in database
'urn:nepomuk:datasource:448659eed398985de3972d3a72c8ac8d',
GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal:
column
nie:url is not unique (strerror of errno (not necessarily
related): No
such file or directory)
As a last choice I'd recommend to dump
previous info and retrigger
indexing with tracker-control -rs, but would be interesting to
know
what's going on there.
Yeah, I have kept that in reserve. If it has to be done, I
guess I will
but I'd like to avoid it if i can, as I am sure you'd imagine.
Thank you for reporting this here. I think this issue is related
to mounted GVFS locations.
I've noticed something strange happening with mount points and
starting tracker. Unmounting them seemed to fix this "blockage"
you talk of.
I've not had time to look into it myself but the errors you report
above give us much more insight as to what's causing this.
The error coming from SPARQL INSERT indicates that nie:url for
subject
<urn:nepomuk:datasource:448659eed398985de3972d3a72c8ac8d>
already exists. The nie:url is a nrl:InverseFunctionalProperty
so it must be unique
(https://git.gnome.org/browse/tracker/tree/data/ontologies/30-nie.ontology#n42)
in the database.
To know this nie:url, Brian could do this:
tracker-sparql -q "select ?url { <urn:nepomuk:datasource:448659eed398985de3972d3a72c8ac8d>
nie:url ?url }"
I'm guessing that Tracker's volume management is trying to insert
a volume for a nie:url that already exists for another resource
(that is or isn't a volume, mountpoint or directory).
I think somewhere here at set_up_mount_point_type:
https://git.gnome.org/browse/tracker/tree/src/miners/fs/tracker-miner-files.c#n720
It's just an idea and some guessing from the reported criticals
vs. context described by Brain, though.
I
thought there was a bug reported about this, but I couldn't find
it/one.
It's quite severe though and should be fixed!
Indeed
Kind regards,
Philip
|
