Re: [Tracker] Tracker-Critical error in the tracker-miner-fs.log

[Martyn Russell <martyn lanedo com>]

On 07/09/11 06:50, John stacy wrote:
> Hello Team,

Hello,

> I am using tracker-0.10.18 on my ubuntu mechine. For this version, I
> added few g_debug messages and installed the tracker.
> After restarting the ubuntu mechine, I am able to observe the complete
> log messages in the tracker-miner-fs.log file for the first time.
>
> Again If I restart the tracker using the below commands
> # tracker-control -r
> # tracker-control -s
>
> I am facing dbus-critical error and after this message the logging stops
> i.e there are no log messages available further, though the tracker
> executes fine.
> *06 Sep 2011, 22:09:29: Tracker-Critical **: Couldn't create new Files
> miner: 'D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is
> already taken, perhaps the application is already running?'*
>
> why am I getting this error?
> is there any other way of starting the tracker apart from the above
> commands?

There is a race condition where the miner is instantiated more than once 
at the same time. That leads to this error. Jürg fixed this in master 
(the logs being overwritten) yesterday and it will be in the 0.10.26 
release tomorrow.

See commit b74b7df2f685bd3e693341c709246719a1ba9849

> How to get the log messages in the tracker-miner-fs file after the
> second restart? (My current verbosity level in all configuration files
> are 3)

You will either have to patch by cherry-picking that commit above or 
wait for 0.10.26 unfortunately (unless you want to use master).

> I am unable to understand the after effects of commenting out the above
> mentioned critical error in the source code
> (*src/miners/fs/tracker-miner-files-index.c *and
> *src/libtracker-miner/tracker-miner-object.c*) as my main goal is to get
> the complete log for miner for every restart.

Yea, this one has bugged me for a while, it should be fine now.

--
Regards,
Martyn

Founder and CEO of Lanedo GmbH.