The site I have has lots of attached documents (like 3.2GB worth) and I'm trying to do an initial indexing of the site. When I do the index it will spin for a while and then crap out. Could it be due to the size of the files? All I have is home/mysite.com/apache-tika with the jar in it, and I'm telling the module that. I haven't done any other config.

I have gotten tika to index as expected with only a handful of these nodes, but when I did the complete upload it stopped wanting to fully index.

--Corey

Comments

coreycondardo’s picture

I have a little more info here -- we are trying to index a large number of files and when we run cron tika is not being called. We know this because we put in a snippit of php code to write to the system log at the end of the tika module and that message never shows up. It does show up when running the index manually.

Additionally, the number of items index does not go up after a cron run.

We also noticed that if we run tika from the command line we get the following error at the top of the output:
INFO - unsupported/disabled operation: EI

The index works as expected without checking the box to index attachments both on cron and by manually indexing.

Any idea what the problem might be?

coreycondardo’s picture

I have a little more info here -- we are trying to index a large number of files and when we run cron tika is not being called. We know this because we put in a snippit of php code to write to the system log at the end of the tika module and that message never shows up. It does show up when running the index manually.

Additionally, the number of items index does not go up after a cron run.

We also noticed that if we run tika from the command line we get the following error at the top of the output:
INFO - unsupported/disabled operation: EI

The index works as expected without checking the box to index attachments both on cron and by manually indexing.

Any idea what the problem might be?

izus’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

this is a two years ago old issue.
didn't succeed to reproduce it.
i belive the last codebase fixed it
please feel free to reopen is the issue persists