Forums / Extensions / eZ Find / Can't re-index existing or new content in Solr
Thanh Nguyen
Monday 10 January 2011 5:12:30 pm
Seems as though around Sept 2010 we were having indexing issue due to the problem mentioned here: http://share.ez.no/forums/extensions/ez-find/indexing-trouble/(language)/eng-GB. I've fixed that. Yes, it's been like that for moths. Now if i run
php extension/ezfind/bin/php/updatesearchindexsolr.php -s admin --clean-all php extension/ezfind/bin/php/updatesearchindexsolr.php -s manage
the only content that's indexed is ones modified before Sept 2010. The only way I can index articles after that is by update an article or creating a new one in EZP. EZP immediately indexes after I hit the "publish" button.
I've tried disabling forking as per http://share.ez.no/forums/extensions/ez-find/solved-ezfind-solr-issues-not-indexing-old-content. But that didn't help.
I've also tried clearing the ezsearch_object_word_link and ezsearch_word tables and running updatesearchindex.php as suggested in http://share.ez.no/forums/setup-design/re-indexing/(language)/eng-GB. No luck.
Are there another ideas out there? Any logs I should looks at during indexing to tell what it's doing? What is the query it uses to determine which content to index?
Bertrand Dunogier
Tuesday 11 January 2011 1:26:45 am
Is there any content in ezsearch_object_word_link and ezsearch_word after you index ? The tables should remain empty, as they aren't used by ezfind, but by the default Exponential search engine.
You can inspect the standard logs, especially the debug and error ones, eZ Find should use them while indexing.
What platform are you on ?
Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Wednesday 12 January 2011 4:46:31 pm
Yes, the tables are still empty.
We're running CentOS 5.3 connecting to MySQL 5.1.48. I'm not sure where to look for the logs you speak of. I ran updatesearchindexsolr.php with --debug and --sql switches and didn't see anything very helpful. And /var/log/solr0.log.0 is empty.
Monday 24 January 2011 6:01:32 pm
It turned out that we had configured eZFind incorrectly and pointed it to the wrong database schema. Problem solved.
Tuesday 25 January 2011 1:47:41 am
Problem solved => can you please mark the topic as solved ? thanks :-)