Ok, restricting trackerd to a small subset of my home directory allowed
the --reindex to finish just fine. I was also then able to search.
Next I updated tracker to svn, and opened it up to my whole home
directory again, and ran --reindex. Woke up this morning to a hung
trackerd...
$
kill -9 can corrupt the index and prevent searching again (until
reindexed)
reindexing should solve the problem
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Results so far... after several hours, but apparently before it was done
indexing, trackerd exit'd with this error:
ERROR: excessive busy count in query GetServiceID and thread main.
Running tracker-status appears to have started trackerd back up again:
$ tracker-status
Tracker daemon's
the bugs with busy count and trackerd status are fixed in svn so maybe
that will help
searching while indexing can produce timeouts - its not really a bug as
such although the error msg should be improved
I would suggest getting a subset of your home directory indexed (set
settings in Tracker
I also have this problem. I upgraded to 7.10 and Tracker worked great--
for about a day. Now it returns no results. Also seems to have tons
indexed.
$ tracker-stats
---fetching index stats-
default : 0
Files : 87202
Folders : 8017
Documents : 9854
Images : 6991
Music : 579
fair enough, I did killall trackerd and --reindex, when the cpu becomes
idle again I did tracker-status:
$ time tracker-status
Tracker daemon's status is �Ë.
real0m25.013s
user0m0.004s
sys 0m0.000s
For some reason the returned status is garbled, trackerd memory
corruption? Also,
okay, works after it finished indexing again.
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ka-Hing,
it might just be update problem from 0.6.2 to 0.6.3
0.6.3 should automatically reindex when upgraded but you must make sure
you do killall trackerd after upgrading to 0.6.3
doing a reindex is what it would do anyhow
--
tracker-search-tool reports no result
There seems to be another problem with this. I'm not getting any search
results at all with the newest tracker. (0.6.3-0ubuntu2)
tracker-stats indicates that I have many files indexed, while tracker-
search-tool or tracker-search can't find any.
[EMAIL PROTECTED]:~$ tracker-stats
use tracker-status to see if indexing is complete
results will only be available when indexing is finished
if no help then also try :
killall trackerd
trackerd --reindex
and wait for index to finish
let us know if problem persists
--
tracker-search-tool reports no result
I am also not able to get any search result. It worked at one point
after 0.6.3, but either a subsequent update broke it, or it just stopped
working on its own. tracker-status returns that tracker is idle, and
tracker-stats gives plenty of stuff indexed. I don't think doing a
--reindex is going to
tracker (0.6.3-0ubuntu1) gutsy; urgency=low
[ Emilio Pozuelo Monfort ]
* New upstream release (LP: #130794, #131983, #132320, #137352, #138331,
#139173, #132505, #131559, #131735, #132710, #133246, #137873, #138778.
* debian/patches/01-version_fix.patch,
updated to 0.6.2-2ubuntu2 and problem still persists, searches return 0
result (both from the tracker-search-gtk and the command line tracker-
search)
also get a bunch of GLib-CRITICAL message mentioned above if I run
trackerd -v 3 -R
--
tracker-search-tool reports no result
fix will be in 0.6.3 release which is due this week
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: tracker (Ubuntu)
Importance: Undecided = Low
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
We noticed this problem and have already fixed in svn
We will have a new release out with this fix shortly
** Changed in: tracker (Ubuntu)
Status: New = Fix Committed
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification
** Attachment added: figure I should upload my config
http://launchpadlibrarian.net/9159698/tracker.cfg
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Some more investigating. Setting verbosity to 2, now I get a bunch of
this for the last 10 minutes (still going!):
06 Sep 2007, 20:19:10:163 - deleting email email://[EMAIL
PROTECTED]/javabsp;uid=8606
06 Sep 2007, 20:19:12:581 - deleting email email://[EMAIL
PROTECTED]/javabsp;uid=8608
06 Sep
Looking at the sqlite db itself it looks like it's populated:
$ sqlite3 file-content.db
sqlite select COUNT(*) from ServiceContents;
6112
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs,
ahh I found ~/.local/share/tracker/tracker.log, but all it has is this:
06 Sep 2007, 19:55:38:935 - ERROR: no matching account found for email
06 Sep 2007, 19:55:38:935 - ERROR: no matching account found for email
06 Sep 2007, 19:55:38:935 - ERROR: no matching account found for email
06 Sep 2007,
running `trackerd -v 3 -R` gives lots of:
(trackerd:4869): GLib-CRITICAL **: g_hash_table_insert: assertion
`hash_table != NULL' failed
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs,
Disabling Evolution indexing makes those hash_table != NULL messages
mostly disappear, but still no search result.
--
tracker-search-tool reports no result
https://bugs.launchpad.net/bugs/137873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
22 matches
Mail list logo
