[Xapian-discuss] upgraded 1.0.19 to 1.2.0 - indexing seems to be getting stuck

[Per Jessen]

Olly Betts wrote:

> On Wed, Jun 02, 2010 at 08:21:03AM +0200, Per Jessen wrote:
>> Olly Betts wrote:
>> 
>> > On Tue, Jun 01, 2010 at 06:14:07PM +0200, Per Jessen wrote:
>> >> Today I upgraded to 1.2.0 - and my indexing jobs are now getting
>> >> hung
>> >> up.  They appear to be waiting on a futex.  Not everyone, but
>> >> every
>> >> now and then.  I'll try to get some diagnostics.
>> > 
>> > Some more details would be useful too - you don't even mention the
>> > OS or language you're using (though I guess Linux if you have
>> > futexes).
>> 
>> Sorry, I tend to forget that.  I'm on Linux and using C++.  I have
>> written a indexing utility that reads files from disk, parses the
>> contents and indexes them.
> 
> Is this run from the command line?  Does it use threads?

Command line yes, threads no.

>> 
>> Interestingly, it seems to be waiting for a fork()ed "/bin/cat" which
>> seems to be happening in backends/flint_lock.cc ?
> 
> That process holds the write lock on the database (to protect us from
> the less helpful semantics of fcntl locking).
> 
> This has tripped up people running under selinux before, so if you're
> using selinux you might need to update your policy for processes using
> Xapian.

No SElinux here, but we do run apparmor - it didn't cause a problem with
1.0.19, but I'll the audit-log.


/Per Jessen, Zürich