Re: [Tracker] Tracker on Solaris

[Martyn Russell <martyn lanedo com>]

On 10/01/13 17:31, Frank Lahm wrote:
> Hi,

Hello Frank,

> I succeeded in getting Tracker to build on Solaris 11, patches
> attached in case anybody is interested. They are not really applicable
> for upstream inclusion, but anybody facing the same task might
> appreciate the pointers.

Great!

The patches look good - I think the first one needs a few #ifndef checks 
around it for flock() but other than that, I think we could commit some 
of those. Thanks.

> I'm using building and using 'master' from git.
>
> I'm using the provided tracker-sandbox script for running Tracker.
> Unfortunately this fails, tracker-control -s throws the following
> error:

The tracker-sandbox script is good, but I would be careful here, in my 
experience, difference shells have different rules and Solaris was 
always a pain in the arse and didn't play consistently well with what 
was expected on Linux.

So if things fail here, I would try separately running daemons first 
(which it looks like you did below):

> root solaris:~# /opt/tracker/bin/tracker\-control -s
>
> Starting miners?
> (tracker-control:15040): Tracker-CRITICAL **: Could not create proxy
> on the D-Bus session bus, Error calling StartServiceByName for
> org.freedesktop.Tracker1.Miner.Applications:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
> /opt/tracker/libexec/tracker-miner-fs exited with status 1
>    ? File System (perhaps a disabled plugin?)
>
> (tracker-control:15040): Tracker-CRITICAL **: No D-Bus proxy found for
> miner 'org.freedesktop.Tracker1.Miner.Applications'
>    ? Applications (perhaps a disabled plugin?)
>
> I've pasted some the results of some debugging to pastie.org:
>
> Using tracker-sandbox:
>
>    <http://pastie.org/private/jvxvvg4ciwg2kibv6nuq1g>
>
> Running libexec/tracker-miner-fs -v 3 -n:
>
>    <http://pastie.org/private/jp8j0cdvy24lskokn4nncg>

Yea, it seems we can't create our session on the bus. This leads me to a 
few questions:

1. Was the name taken? - Usually we would get an error for that case, 
but I would check anyway.

2. Does the daemon with that address exist and is it running?

3. Are you able to test other dbus programs with your session and can 
they "register"? A test program to do this should be only a few lines of 
code.

The errors look quite endemic of environment or set up issues, but I am 
speculating based on experience.

> I'd highly appreciate any hint. Otherwise I have to give up with
> Tracker > 0.6.x and go back to trying to use the system 0.6.

Yea, the dbus side really needs to be checked/working well. I did create 
my own sandbox script to be able to run separate instances of Tracker 
with separate configurations, etc. It's still unfinished, but I found 
that Python was a safer option and easier to make sure the environment 
was how I wanted it. Each to their own though :)

--
Regards,
Martyn

Founder and CEO of Lanedo GmbH.