Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Here are the errors now appearing on admin/settings/luceneapi_node/statistics:
* Error thrown in /srv/drupal/sites/mysite/modules/luceneapi/luceneapi.admin.inc on line 429.
* warning: array_unshift() [function.array-unshift]: The first argument should be an array in /srv/drupal/sites/mysite/modules/luceneapi/contrib/luceneapi_node/luceneapi_node.module on line 219.
These errors first appeared when I launched a rebuild index batch process and it crashed after exceeding our php.ini maximum execution time. I then disabled, uninstalled and reinstalled the module (via drush), set my max execution time to ten minutes.
The batch process appeared to successfully complete, but these errors are now showing up again.
Unfortunately, I discovered a watchdog bug at the same time, so I have no log entries for the index process.
Any thoughts?
Comments
Comment #1
sfyn commentedAnd all my lucene searches now throw the following error:
Error thrown in /srv/drupal/sites/mysite/modules/luceneapi/contrib/luceneapi_node/luceneapi_node.module on line 415.
Comment #2
cpliakas commentedHi sfyn.
Thanks for posting all of the error messages. In terms of the original post, it seems that the index cannot be opened. Generally the reason why the index cannot be opened is displayed before the "Error thrown in ..." part of the message, but I am unsure as to why that is not getting displayed. To narrow down the problem, your error is originating in the luceneapi_index_open() function in luceneapi.module. This is also the case with the comment #1. I will take a look at the error handling mechanism to make sure it is working as expected.
I would manually delete the sites/default/files/luceneapi_node directory (or whatever location you have the index set to) and reindex the content, as the index could be corrupt. Also, is your files directory located on a network share by any chance, such as NFS?
Thanks,
Chris
Comment #3
cpliakas commentedAdded code to eliminate the second error in cases where the index cannot be opened at #287886.
Comment #4
cpliakas commentedAdded code to eliminate the second error in cases where the index cannot be opened at #287886.
Comment #5
sfyn commentedGreat, thanks for the quick followup.
The file was on a debian ext3fs filesystem. I did in fact disable the module and delete the indexes - now I am re-indexing with cron jobs and it appears to be working normally.
Comment #6
cpliakas commentedGreat! Thanks for the follow-up. The reason why I asked the filesystem question is because the Zend_Search_Lucene component makes use of the flock() function which does not work on most networked filesystems.
Thanks,
Chris