Hi, Just a note to let you know that I am using trackerd on the desktop hosts instead of running a seperate server just for indexing. Each hosts servers desktops to about 8 users simultaneously and I have had no problems at all with trackerd.
Thank you very much for your work. Chris. On Tue, Nov 11, 2008 at 2:40 PM, Chris Fanning <christopher.fann...@gmail.com> wrote: > Hi, > >> Well, we don't use PID files, we use DBus to manage if we are already >> running or not. So if it comes back with that error, then it means there >> is already a session running and the Tracker name is already in use. > ok. sorry, some had escaped me. > >> Do they share the same /var? The only reason I ask, is that DBus has >> files in there which could be causing the "already running" issue. >> > no. > > > This is the fisrt time I've had to deal with dbus, please bear with me. > > scenario 1. > start out fresh. > 1) kill all trackerd processes on desktop_server > 2) kill all trackerd on index_server > > Then on (headless) index_server > su - user > dbus-launch trackerd > > note: I'm using dbus-launch because trackerd will not launch dbus on > its own reporting: > DBUS ERROR: org.freedesktop.DBus.Error.Spawn.ExecFailed occurred with > message dbus-launch failed to autolaunch D-Bus session: Autolaunch > error: X11 initialization failed. > ERROR: could not get the dbus session bus - exiting > > Now on desktop_server. > $tracker-search-tool > I try to search for something and it replies "Process > /usr/bin/trackerd exited with status 0" > > Remember I have wrapped trackerd on the desktop_server to avoid > indexing from the desktop_server > more /usr/bin/trackerd > #!/bin/bash > /usr/bin/trackerd.orig --no-indexing > > At this point is seems trackerd is failing to start on desktop_server. > So on index_server, I kill trackerd. > Now on desktop_server I run "tracker-search-tool" again and it works! > ps -e |grep tracker confirms is is running. > > scenario 2. > The reverse. > I kill everything. > Then run tracker-search-tool on desktop_server (searches correctly) > and then I try to start it on index_server. It starts but says: > Initialising tracker... > ** (trackerd:1582): WARNING **: Tracker daemon is already running - > attempting to run in readonly mode > > If I go back to desktop_server and kill trackerd, then go to > index_server, I can start trackerd ok. > > As you can appreciate, I'm quite lost as to what's happening. There > are dbus'es running on different servers. But they do indeed seem to > be comunicating. > > Sorry about the mess. > Thanks. > Chris. > > On Tue, Nov 11, 2008 at 1:42 PM, Martyn Russell <mar...@imendio.com> wrote: >> Chris Fanning wrote: >>>> The daemon should start itself, is there actually another process >>>> already started at this point? >>> after entering via 'su - username', the only processes running under >>> 'username' are >>> 1. su >>> 2. bash >>> trackerd does not start dbus by itself, that's why I use "dbus-launch >>> trackerd" >> >> Sure, but I would expect DBus to be running a session bus already. I >> would expect to see this: >> >> mar...@petunia:~$ ps -C dbus-daemon -o pid,uid,cmd >> PID UID CMD >> 5186 103 /usr/bin/dbus-daemon --system >> 6232 1000 dbus-daemon --fork --print-address 20 --print-pid 22 --session >> >>>> Ah, that's TRUE. Note. If you call the Tracker DBus API, it should start >>>> it for you. I would advise not starting it yourself, >>> Maybe trackerd is finding a PID file or lockfile someplace? If both >>> trackerd on index_server and desktop_server are reading the same file >>> that might explain it. >> >> Well, we don't use PID files, we use DBus to manage if we are already >> running or not. So if it comes back with that error, then it means there >> is already a session running and the Tracker name is already in use. >> >>>> and just using the >>>> config option to disable indexing instead. >>> >>> The reason I asked about passing a different config to trackerd was >>> because of this. Both the desktop_server and the index_server share >>> the same /home. >> >> Do they share the same /var? The only reason I ask, is that DBus has >> files in there which could be causing the "already running" issue. >> >> -- >> Regards, >> Martyn >> > _______________________________________________ tracker-list mailing list tracker-list@gnome.org http://mail.gnome.org/mailman/listinfo/tracker-list
