Re: [Tracker] Could not create FTS delete statement:
On Thu, 2017-03-02 at 17:43 +0100, Carlos Garnacho wrote: > Hi Chris, > > On Thu, Mar 2, 2017 at 3:24 PM, Chris <cpoll...@embarqmail.com> > wrote: > > > > Could someone be kind enough to tell me what this warning means? > > The > > complete line reads: > > > > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > > store:4352): Tracker-WARNING **: Could not create FTS delete > > statement: > > table fts5 has no column named nco:hobby > > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > > store:4352): Tracker-WARNING **: Could not create FTS delete > > statement: > > table fts5 has no column named nco:hobby > > This started appearing in some systems due to a glitch in the change > from fts4 to fts5, tracker had to trigger a change in full-text > indexed fields, and nco:hobby was the innocent victim. > > But it does seem like the file ~/.cache/tracker/ontologies.gvdb > (containing a cache of the current ontology) didn't get updated > properly in some cases, which means that tracker still deals with > that > property as if it were fts-indexed, while it's no longer the case. > > > > > > > I'm very sure it's harmless but as one who looks at his syslog > > closely > > its one of those petty annoyances that bites into my OCD that I > > know > > shouldn't be there. > > You can get rid of it by doing: > tracker daemon -t > rm ~/.cache/tracker/ontologies.gvdb > tracker daemon -s > > That should get that file rebuilt from scratch, containing the > up-to-date ontology. I would have liked to do something from the > Tracker side, but that requires yet another change in FTS fields, and > those happen rarely... > > Cheers, > Carlos > I ran your command(s) above right after you sent them Carlos however this is still appearing Mar 6 10:54:20 localhost org.freedesktop.Tracker1[12808]: (tracker- store:13115): Tracker-WARNING **: Could not create FTS delete statement: table fts5 has no column named nco:hobby Mar 6 10:54:20 localhost org.freedesktop.Tracker1[12808]: (tracker- store:13115): Tracker-WARNING **: Could not create FTS delete statement: table fts5 has no column named nco:hobby -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 10:58:27 up 3 days, 19:26, 2 users, load average: 0.16, 0.17, 0.18 Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-65-generic signature.asc Description: This is a digitally signed message part ___ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
Re: [Tracker] Could not create FTS delete statement:
On Thu, 2017-03-02 at 17:43 +0100, Carlos Garnacho wrote: > Hi Chris, > > On Thu, Mar 2, 2017 at 3:24 PM, Chris <cpoll...@embarqmail.com> > wrote: > > > > Could someone be kind enough to tell me what this warning means? > > The > > complete line reads: > > > > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > > store:4352): Tracker-WARNING **: Could not create FTS delete > > statement: > > table fts5 has no column named nco:hobby > > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > > store:4352): Tracker-WARNING **: Could not create FTS delete > > statement: > > table fts5 has no column named nco:hobby > > This started appearing in some systems due to a glitch in the change > from fts4 to fts5, tracker had to trigger a change in full-text > indexed fields, and nco:hobby was the innocent victim. > > But it does seem like the file ~/.cache/tracker/ontologies.gvdb > (containing a cache of the current ontology) didn't get updated > properly in some cases, which means that tracker still deals with > that > property as if it were fts-indexed, while it's no longer the case. > > > > > > > I'm very sure it's harmless but as one who looks at his syslog > > closely > > its one of those petty annoyances that bites into my OCD that I > > know > > shouldn't be there. > > You can get rid of it by doing: > tracker daemon -t > rm ~/.cache/tracker/ontologies.gvdb > tracker daemon -s > > That should get that file rebuilt from scratch, containing the > up-to-date ontology. I would have liked to do something from the > Tracker side, but that requires yet another change in FTS fields, and > those happen rarely... > > Cheers, > Carlos Thanks Carlos, I really hate to keep being a PITA with all these warning questions. I must say though this is a very friendly list and very helpful. That said, here's another one I've begun seeing Mar 2 11:14:36 localhost org.freedesktop.Tracker1[3934]: (tracker- store:19787): Tracker-WARNING **: Could not insert FTS text: constraint failed (strerror of errno (not necessarily related): No such file or directory) -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 11:17:52 up 3:41, 1 user, load average: 0.14, 0.23, 0.20 Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-65-generic signature.asc Description: This is a digitally signed message part ___ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
Re: [Tracker] Could not create FTS delete statement:
Hi Chris, On Thu, Mar 2, 2017 at 3:24 PM, Chris <cpoll...@embarqmail.com> wrote: > Could someone be kind enough to tell me what this warning means? The > complete line reads: > > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > store:4352): Tracker-WARNING **: Could not create FTS delete statement: > table fts5 has no column named nco:hobby > Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- > store:4352): Tracker-WARNING **: Could not create FTS delete statement: > table fts5 has no column named nco:hobby This started appearing in some systems due to a glitch in the change from fts4 to fts5, tracker had to trigger a change in full-text indexed fields, and nco:hobby was the innocent victim. But it does seem like the file ~/.cache/tracker/ontologies.gvdb (containing a cache of the current ontology) didn't get updated properly in some cases, which means that tracker still deals with that property as if it were fts-indexed, while it's no longer the case. > > I'm very sure it's harmless but as one who looks at his syslog closely > its one of those petty annoyances that bites into my OCD that I know > shouldn't be there. You can get rid of it by doing: tracker daemon -t rm ~/.cache/tracker/ontologies.gvdb tracker daemon -s That should get that file rebuilt from scratch, containing the up-to-date ontology. I would have liked to do something from the Tracker side, but that requires yet another change in FTS fields, and those happen rarely... Cheers, Carlos ___ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
[Tracker] Could not create FTS delete statement:
Could someone be kind enough to tell me what this warning means? The complete line reads: Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- store:4352): Tracker-WARNING **: Could not create FTS delete statement: table fts5 has no column named nco:hobby Mar 2 08:20:18 localhost org.freedesktop.Tracker1[3934]: (tracker- store:4352): Tracker-WARNING **: Could not create FTS delete statement: table fts5 has no column named nco:hobby I'm very sure it's harmless but as one who looks at his syslog closely its one of those petty annoyances that bites into my OCD that I know shouldn't be there. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 08:21:11 up 44 min, 1 user, load average: 0.12, 0.18, 0.80 Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-65-generic signature.asc Description: This is a digitally signed message part ___ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
