Zebra indexing problems
I'm seeing some rather odd indexing problems with incremental indexing and Koha 3.12.05. I have everything set up with Zebra 2.0.56 and Yaz 5.0.9. Full indexing works fine and incremental indexing logs the fact that changes are seen and should be applied. And I've had incremental indexing work sometimes, but very seldom. Most changes are simply not being found when I search in the OPAC. Even after the data and incremental index changes, the old values are still being found rather than the new. Has anyone seen such indexing problems before? What can I be checking to track this problem down and address it? Thanks, Tom -- ----------------------------------------------------------------------------- Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 208 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 Happy New Year!! -----------------------------------------------------------------------------
Tom Hanstra schreef op ma 06-01-2014 om 13:35 [-0500]:
Has anyone seen such indexing problems before? What can I be checking to track this problem down and address it?
What do your logs say? In particular, is the cron job for indexing actually running, and are emails from cron (which will talk about errors from the scripts) actually going somewhere where you can see them? -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
It looks like this was tracked to a problem with paths and environment. I found that the testing which worked was when I was running interactively, whereas the times which did not work were when I was running using cron. Once I made sure my base shell was getting the right paths and environment information for the cron processes, they were able to run properly. Robin: Thanks for checking in. My internet access here in the frozen midwest was limited Monday and Tuesday, hence my late reply. Tom On 1/6/14 5:05 PM, Robin Sheat wrote:
Tom Hanstra schreef op ma 06-01-2014 om 13:35 [-0500]:
Has anyone seen such indexing problems before? What can I be checking to track this problem down and address it? What do your logs say? In particular, is the cron job for indexing actually running, and are emails from cron (which will talk about errors from the scripts) actually going somewhere where you can see them?
-- ----------------------------------------------------------------------------- Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 208 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 Happy New Year!! -----------------------------------------------------------------------------
participants (2)
-
Robin Sheat -
Tom Hanstra