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

Olly Betts olly at survex.com
Wed Jun 2 13:48:57 BST 2010


On Wed, Jun 02, 2010 at 09:20:21AM +0200, Per Jessen wrote:
> Per Jessen wrote:
> 
> >>> 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.
> 
> Nothing found in the audit-log. 

This is rather odd - nobody else has reported issues (and Linux is probably
the most used platform for Xapian), and the locking code really hasn't changed
much between 1.0.19 and 1.2.0.

I don't have any good ideas of what might be going on.  You could try with
this patch which prevents /bin/cat being used - if that fixes it, we have
something to go on, and if not we might at least get a better backtrace:

http://oligarchy.co.uk/xapian/patches/xapian-1.2-no-exec-bin-cat.patch

Otherwise I think you'll have to work out what is going on here, as only you
can reproduce it.  Think about what might be different for you and try changing
that to see if it helps (e.g. you could try 1.0.20 and 1.1.x).

Cheers,
    Olly



More information about the Xapian-discuss mailing list