tracker searches sometimes don't work, reporting "Process /usr/bin/trackerd exited with status 0"

[Vincenzo Ciancia]

Binary package hint: tracker

I am running gutsy, with tracker 0.6.3. The problem I am describing was here since tribe5 at least (I installed that). Sometimes tracker just does not work. Trackerd is running, however I don't see live results in deskbar, and if I run tracker-search-tool I get

Process /usr/bin/trackerd exited with status 0

which is strange, since 0 is "success" under usual conventions. However, if I run tracker-search (in the tracker-utils package) I get

tracker-search: internal tracker error: Process /usr/bin/trackerd exited with status 0

I have no log in .local/share/tracker.

[Jamie McCracken (jamiemcc-blueyonder)]

that error means you are spawning a new version of trackerd which exits because a trackerd version is already there

it could be when you upgraded to 0.6.3 you still have an old version of trackerd running

try killall -9 trackerd and then launch trackerd in a terminal

[Vincenzo Ciancia (vincenzo-ml)]

As I said, this happens "sometimes" and was "here since tribe5", hence I think since tracker 0.6.1 at least.

"Sometimes", more precisely, means once every two or three days, and with reboots in between. The workaround, you're right, is to kill trackerd and restart it, but it's surely a bug. Maybe the running tracker daemon stayed there from an old session? If so, tracker should record the display and the pid of each instance in a temporary file, so that if you are going to start a new copy on the same display, you know you can kill it.

[Jamie McCracken (jamiemcc-blueyonder)]

there were problems with earlier versions not dying when the session ended

0.6.3 however should die nicely when session ends - if not pls let me know if it persists after logging out

[parren (peter-arrenbrecht)]

I am seeing this in Gutsy Beta. Never was able to run a tracker search at all, actually.

[parren (peter-arrenbrecht)]

Did the killall -9 trackerd as suggested above. Now I get no search results, and once I got

  ** (trackerd:29041): CRITICAL **: tracker_get_hit_counts: assertion `query->words' failed

when trying to run a search.

[Jamie McCracken (jamiemcc-blueyonder)]

the critical is cause you tried to search for a stopword which are not indexed - in next version we will indicate if search term is a stopword

try using your user name to search

[anubhavrakshit (anubhavrocks)]

I have the same problem,also i notice that when i auto start tracker(by putting tracker in System->Prefrences->Sessions) commands like tracker-stats and tracker-status do not work and give an error.If i kill trackerd and restart it things start working okay.Also if i start trackerd from .gnomerc it works fine.

[anubhavrakshit (anubhavrocks)]

Now i get a new error message
anubhav@anubhav-laptop:~$ tracker-stats

** (tracker-stats:4653): WARNING **: tracker-stats: an error has occured: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

anubhav@anubhav-laptop:~$ tracker-status
Tracker daemon's status is �Ë
.

[Kaihsu Tai (kaihsu)]

I had the same error message ‘Process /usr/bin/trackerd exited with status 0’; but after removing the lock file .local/share/tracker/kaihsu_tracker_lock and re-running tracker-search-tool, it worked.

[Simon Ryu (neocoin)]

Thank you Kaihsu Tai

I had upgrade feisty fawn to gutsy gibbon in last Friday. I have same problem.

[Chris D (cdekter)]

Definitely present in Gutsy as released. Was able to correct it by deleted the lock file as described by Kaihsu

[Kaihsu Tai (kaihsu)]

Sometimes it took a long time for tracker-search-tool to give this error message without any results ‘Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.’ Then:

clc:~ $ tracker-status
Tracker daemon's status is �Ë
.

This is the same as what anubhavrakshit wrote on 2007-10-12.

[Sergio Zanchetta (primes2h)]

Same problem here on Gutsy release.

Workaround from Kaihsu works.

[era (era)]

This is pretty severe. On a fresh Gutsy install, opening Applications - Accessories - Tracker Search Tool and typing in a random search phrase displays this error dialog.

There is no way a new user would know not to panic at this, and there is certainly no useful information for a non-technical user in the error dialog. "Yikes, what did I do, did I break it!?"

[Jamie McCracken (jamiemcc-blueyonder)]

we use lockf to lock the lockfile to prevent another instance of trackerd running.

unless lockf is broken (on NFS) the lock should be released whenever trackerd exits or is killed

I need more info - IE are you using it on NFS?

Can you also check if another instance of trackerd is running on another NFS session to the same home dir

[era (era)]

No NFS here. Like I wrote above, pretty much out of the box Gutsy fresh install.

[era (era)]

era@indeed:~$ ls -l .local/share/tracker/
total 8
drwxr-xr-x 2 era era 4096 2007-10-25 22:16 data
-rw------- 1 era era 0 2007-10-24 08:33 era_tracker_lock
-rw------- 1 era era 780 2007-10-25 20:57 tracker.log
era@indeed:~$ sudo ps wallx | fgrep tracker
[sudo] password for era:
0 1000 1085 9552 17 0 2972 644 - R+ pts/0 0:00 grep -F tracker
0 1000 5133 1 34 19 27892 8188 - SNl ? 0:05 trackerd

The machine has crashed once or twice while I was fiddling with getting suspend and hibernate to work correctly (turned out I needed to disable Compiz ... how obvious </sarcasm>) but other than that, I have only run gedit and terminal (and now Firefox) and idly opened up few of the items in the menus just to look at them,

I had looked at the preferences a couple of times, but otherwise have not touched anything which had "tracker" in it before I tried the search for the first time just before commenting here.

Wait, there is something about it near the very beginning of .xsession-errors.

So if I killed my X session with ctrl-alt-backspace and logged in again, would that result in two competing trackerd:s? That would explain it. Like I wrote before, I was struggling with suspend/hibernate problems. (See also bug #133118.)

[era (era)]

I don't imagine the log will be useful, but attaching it just in case.

[Jamie McCracken (jamiemcc-blueyonder)]

** (trackerd:9464): WARNING **: Tracker daemon is already running - exiting

in your xsession-errors reveals trackerd is already running hence the new dbus session wont pick up the old one nor can it activate a new one

Does anyone get this error and has not killed their session?

[Sergio Zanchetta (primes2h)]

2007/10/25, Jamie McCracken <email address hidden>:
> ** (trackerd:9464): WARNING **: Tracker daemon is already running -
> exiting
>
> in your xsession-errors reveals trackerd is already running hence the
> new dbus session wont pick up the old one nor can it activate a new one
>
> Does anyone get this error and has not killed their session?
>
> --
> tracker searches sometimes don't work, reporting "Process /usr/bin/trackerd exited with status 0"
> https://bugs.launchpad.net/bugs/148118
> You received this bug notification because you are a direct subscriber
> of the bug.
>

When I got that message I had added another path to index in tracker,
coming from a windows partition in LAN mounted by smbmount.
If it can help.

[Vincenzo Ciancia (vincenzo-ml)]

Jamie: when it happens, I think that I have tracker running from an old session. The fact that many applications using dbus stay alive after logging out, and then break at next login, is well known, reported in many places but nobody seems to be investigating the problem. This is perhaps an instance of the same problem.

[era (era)]

FWIW, I posted a separate bug about making the error message a little less intimidating. Bug #157525

[Jamie McCracken (jamiemcc-blueyonder)]

Vincenzo,

gnome-session should kill trackerd when you log out normally - if you crash out with ctrl+alt+backspace then restart X then the trouble starts...

can you confirm if this is the case?

Also pls wait for 10 secs before logging back in to make sure trackerd has exited after logout

[Gregor (aguafuertes)]

I wanted to report the same issue on a fresh Gutsy install.

After reading the comments here, I can confirm that the trouble in my case started after I had killed X with crtl+alt+backspace and logged in again - another (normal) log out after that and log in did not resolve the issue. Does that mean that, once I restarted X with crtl+alt+backspace, I have this issue?

Btw, the workaround described by Kaihsu does not work for me - after I delete the lock file, I can search with tracker, but only see the number of search results in the categories (files, folders, documents), without being able to see the single results. When I click one of the categories, I get the follow warnings (when running tracker from a terminal):

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 79

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 107

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 109

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 109

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 109

(tracker-search-tool:6774): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 109

[Jamie McCracken (jamiemcc-blueyonder)]

Gregor,

Please move your mouse to the right hand side of the window and move the separator to the left (thats why you cant see the results)

[Gregor (aguafuertes)]

Jamie,

that's embarrasing, but I'm just not familiar with GtK-warnings - thanks a lot for pointing it out! I actually never toyed with the separators, so I'm still a bit puzzled why this happened.

Anyway, I tried again and can confirm the behavior you predicted:

- if I kill X with Ctrl+alt+backspace and then login again, I get the error message and have to kill trackerd. Starting up trackerd again and using the GUI search then works, but with the mixed up separator setting.

- if I log out normally, I have no problems after the next login.

[huiii (a00ps)]

high!

when running tracker on fresh ubuntu-gutsy install. the results are not displayed.
it searches though and it shows how much hits it made, but nothing else!! what should i do
?

[Gregor (aguafuertes)]

huiii,

that sounds like the problem described above, where only the left hand column of the tracker GUI is visible.

Move the mouse to the right border of the tracker window. There you should be able to drag a separator to the left -> the right hand side with the search results should become visible.

[Michael Roy (mikemlp)]

I have a fresh gutsy install and I get a very strange error:
:~$trackerd &
[1] 26658
:~$

Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (<email address hidden>)

This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt

Initialising tracker...
Could not set idle IO priority...attempting best effort 7 priority
Throttle level is 0

...
ERROR: CreateService uri is email://1194392263.15384.0@mike-laptop/INBOX;uid=665
ERROR: failed to save email email://1194392263.15384.0@mike-laptop/INBOX;uid=665
ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19
ERROR: CreateService uri is email://1194392263.15384.0@mike-laptop/INBOX;uid=666
ERROR: failed to save email email://1194392263.15384.0@mike-laptop/INBOX;uid=666
ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19
ERROR: CreateService uri is email://1194392263.15384.0@mike-laptop/INBOX;uid=668
ERROR: failed to save email email://1194392263.15384.0@mike-laptop/INBOX;uid=668
ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19
ERROR: CreateService uri is email://1194392263.15384.0@mike-laptop/INBOX;uid=669
ERROR: failed to save email email://1194392263.15384.0@mike-laptop/INBOX;uid=669
Segmentation fault (core dumped)
:~$

Apparently, I have files indexed, but any search I do finds 0 files.

[Michael Roy (mikemlp)]

It would probably be best to disregard my previous post, since it is not related to this particular bug. Apologies to all, it is most likely time for a nap. :)

[Xvani (fredrile+launchpad)]

This happens to me as well. Just posting this to let you know others are experiencing the problem.

[Betes (ben-t-scully)]

Just to confirm, I had the same problem also after using ctrl+alt+backspace to restart X. Killing tracker from the command line worked.

[Emilio Pozuelo Monfort (pochu)]

This bug should be fixed in tracker 0.6.4, which is now in Hardy. Could someone please confirm it?

Thanks

[Emilio Pozuelo Monfort (pochu)]

Closing as fix released.