[Hardy Tracker 0.6.6] "Could not connect to search service as it may be busy"

[Detlef Lechner]

Binary package hint: tracker

[Hardy] Tracker Search Tool 0.6.6] reports sometimes: "Could not connect to search service as it may be busy" if there are > ~100 hits, I try to go through them in groups of ten and Tracker Search Tool tries to display the environment string in a large document. In that case one of the two arrows in the upper right will not grey out. How can I narrow down the error condition and troubleshoot?
 lsb_release -rd: Ubuntu 8.04
detlef@Amilo7600:~$ apt-cache policy tracker
tracker:
  Installiert:0.6.6-0ubuntu3
  Mögliche Pakete:0.6.6-0ubuntu3
  Versions-Tabelle:
 *** 0.6.6-0ubuntu3 0
        500 http://de.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

3) I expect that Tracker shows the environment of the search term as it usually does if there are only a few hits in small documents.
4) Tracker does not show the environment of the search term as it usually does if there are only a few hits in small documents. Instead the environment is not shown and in the upper right both arrows are full blue.

[Ivo Cavalcante (iscc)]

Experiencing same behavior here. Im my case, though, there is a large collection of pdf files, some with 1000+ pages. The first ten results of a query are displayed (no environment of the search terms), but browsing trough the others result sets trigger the messages. In some cases, on the next ten results; in others, I can dig a little more.

Another strange behavior I noticed is that search tool show results in more than one category (in some searchs), but selecting some on the left panel - usually the ones with onjy a few results - brings to me an empty result set on the right panel! When this happen, it's almost certain that the error will trigger if I browse items on a categoty with more numerous results.

Any way I can help bring "more light", please shout... :-)

[Detlef Lechner (detlef-lechner)]

I could not make the contents of ~/.cache/tracker/file-update-index.db vanish by restarting trackerd normally.

[Oka Kurniawan (oka-kurniawan)]

I am experiencing the same behaviour. I can't get any results, it keep on displaying the error message cannot connect to search service. Strangely it happens only recently. I do not know what causes this. Any help?

[Psykotik (linux-ikiru)]

I experience the very same bug since hardy upgrade. I tried to uninstall an re-install tracker, with no luck.

In my case, it doesn't seem to be related to the number of results, but to the category "refining" selection instead; when I select one of the result's category (email, documents, etc), it stays stuck a while and then reports "Could not connect to search service as it may be busy".

[vajorie (vajorie)]

same here - spits that error in a search with too many results if I click the next button or one of the categories. how can we help debug this? makes trackerd pretty much useless for me (now looking for replacements).

[vajorie (vajorie)]

quick addition- when this happens, cpu spikes and stays at 100%

[Saeid Zebardast (saeidzebardast)]

Confirmed on:
Ubuntu 8.04.1
tracker 0.6.6-0ubuntu3.8.04.1
tracker-search-tool 0.6.6-0ubuntu3.8.04.1

[Nicholas Allen (nick-allen)]

I'm seeing this after performing a fresh install of Ubuntu 8.10.

[Mario Italo (marioitalo)]

I'm seeing this too. I'm using Ubuntu 8.10.

[Magnetizer (magnetizer)]

I can confirm this with Ubuntu 8.10 fresh install.

Also the tracker magnifying glass on the panel doesn't show that the tracker is idle. On mouse over it keeps saying "Tracker : Indexing 11/11 folder". It just doesn't finish the indexing process. I tried several times to "reindex" my home directory.

Perhaps this is useful in tracking the problem. If you need more information, just let met know.

Kind regards,

Andre

[Julio Pedreira (julio.pedreira)]

Same here, Ubuntu 8.10.

When trackerd launched from console with "-v 3", this is the output:

Timeout in tracker_dbus_method_search_suggest
Suggested spelling for TEXTO ereg_virutal is TEXTO ereg_virutal.
*** glibc detected *** trackerd: free(): invalid next size (fast): 0xb61548c8 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7b223f4]
/lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb7b24456]
/usr/lib/libglib-2.0.so.0(g_free+0x36)[0xb7ca7c06]
trackerd[0x8056006]
trackerd[0x8056278]
trackerd[0x8070b25]
trackerd[0x8050024]
/usr/lib/libglib-2.0.so.0[0xb7cca02f]
/lib/tls/i686/cmov/libpthread.so.0[0xb7c1750f]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0xb7b947ee]
======= Memory map: ========
08048000-080a4000 r-xp 00000000 08:02 1055885 /usr/bin/trackerd
080a4000-080a5000 r--p 0005b000 08:02 1055885 /usr/bin/trackerd
080a5000-080af000 rw-p 0005c000 08:02 1055885 /usr/bin/trackerd
09da7000-09e6d000 rw-p 09da7000 00:00 0 [heap]
b60a2000-b60af000 r-xp 00000000 08:02 784958 /lib/libgcc_s.so.1
b60af000-b60b0000 r--p 0000c000 08:02 784958 /lib/libgcc_s.so.1
b60b0000-b60b1000 rw-p 0000d000 08:02 784958 /lib/libgcc_s.so.1
b60c5000-b6100000 rw-p b60c5000 00:00 0
b6100000-b6159000 rw-p b6100000 00:00 0
b6159000-b6200000 ---p b6159000 00:00 0
b623a000-b68fd000 rw-p b623a000 00:00 0
b68fd000-b68fe000 ---p b68fd000 00:00 0
b68fe000-b70fe000 rw-p b68fe000 00:00 0
b70fe000-b70ff000 ---p b70fe000 00:00 0
b70ff000-b78ff000 rw-p b70ff000 00:00 0
b78ff000-b7909000 r-xp 00000000 08:02 802634 /lib/tls/i686/cmov/libnss_files-2.8.90.so
b7909000-b790a000 r--p 00009000 08:02 802634 /lib/tls/i686/cmov/libnss_files-2.8.90.so
b790a000-b790b000 rw-p 0000a000 08:02 802634 /lib/tls/i686/cmov/libnss_files-2.8.90.so
b790b000-b7914000 r-xp 00000000 08:02 802638 /lib/tls/i686/cmov/libnss_nis-2.8.90.so
b7914000-b7915000 r--p 00008000 08:02 802638 /lib/tls/i686/cmov/libnss_nis-2.8.90.so
b7915000-b7916000 rw-p 00009000 08:02 802638 /lib/tls/i686/cmov/libnss_nis-2.8.90.so
b7916000-b791d000 r-xp 00000000 08:02 802630 /lib/tls/i686/cmov/libnss_compat-2.8.90.so
b791d000-b791e000 r--p 00006000 08:02 802630 /lib/tls/i686/cmov/libnss_compat-2.8.90.so
b791e000-b791f000 rw-p 00007000 08:02 802630 /lib/tls/i686/cmov/libnss_compat-2.8.90.so
b7929000-b7933000 r--p 00000000 08:02 1324926 /usr/share/locale-langpack/es/LC_MESSAGES/glib20.mo
b7933000-b7934000 rw-p b7933000 00:00 0
b7934000-b793b000 r--p 00000000 08:02 1324805 /usr/share/locale-langpack/es/LC_MESSAGES/tracker.mo
b793b000-b797a000 r--p 00000000 08:02 1081427 /usr/lib/locale/es_ES.utf8/LC_CTYPE
b797a000-b7a5b000 r--p 00000000 08:02 1081481 /usr/lib/locale/es_ES.utf8/LC_COLLATE
b7a5b000-b7a5d000 rw-p b7a5b000 00:00 0
b7a5d000-b7a85000 r-xp 00000000 08:02 785008 /lib/libpcre.so.3.12.1
b7a85000-b7a86000 r--p 00027000 08:02 785008 /lib/libpcre.so.3.12.1
b7a86000-b7a87000 rw-p 00028000 08:02 785008 /lib/libpcre.so.3.12.1
b7a87000-b7a89000 r-xp 00000000 08:02 802623 /lib/tls/i686/cmov/libdl-2.8.90.so
b7a89000-b7a8a000 r--p 00001000 08:02 802623 /lib/tls/i686/cmov/libdl-2.8.90.so
b7a8a000-b7a8b000 rw-p 00002000 08:02 802623 ...

[Tero Karvinen (karvinen+launchpad)]

Same symptoms with Karmic: "Could not connect to search service as it may be busy". I have Ubuntu 10.04 LTS, x86_64, tracker 0.6.95-1ubuntu6, tracker-search-tool 0.6.95-1ubuntu6 and tracker-utils 0.6.95-1ubuntu6.

This looks very similar to Ubuntu bugs #369428 "Can not enable indexing" and bug #568033 "org.freedesktop.Tracker not provided by any .service files, search impossible". I have symptoms from all three bugs at the same time.