[Xapian-discuss] omindex killed

[Olly Betts]

On Sat, Dec 29, 2012 at 10:15:29AM -0400, Chris Purves wrote:
> On 29/12/2012 10:04 AM, Rob Nagler wrote:
>>> Killed
>>
>> That's usually running out of resources.  What does "ulimit" say?  If
>> this is your box, you can set higher limits.  If it is not your box,
>> you'll need to partition your indexing.
>
> ulimit returns unlimited

Internally omindex sets a ulimit for child processes which run external
filters (like pdftotext), though the parent omindex process should deal
with this situation and continue indexing.  So I'm doubtful that's the
problem.

I'd suggest running under gdb:

$ gdb --args omindex --db <and other args>
[...]
(gdb) run

And then when it crashes you can get a backtrace with "bt" to see where
it crashes ("bt full" will show more information, if it's available).

It's helpful to have debug symbols, so if your omindex is stripped it
might be worth rebuilding it.

Cheers,
    Olly