No indexing and "Cannot redeclare class Zend_Search_Lucene_Analysis_Analyzer" #17
Comments
@butonic Any idea? |
that class is installed on the system an collides with the class we ship as part of the app. @JohnnyricoMC Can you try to remove/uninstall the class living in /usr/share/php/Zend/Search/Lucene/Analysis/Analyzer.php? wild guess:
@butonic @karlitschek this is why we should introduce composer - composer's autoloader will avoid such collitions |
Thanks for the suggestion @DeepDiver1975. On a new test user we do see indexes being created in the Unfortunately when performing these actions now, nothing is written to owncloud.log or to the Apache error logs to give a hint, even in loglevel 0. |
@JohnnyricoMC The lucene_index folder contains a lucene index. You can have a look at what is stored with Luke - Lucene Index Toolbox. If you can spare the time, could you review #1 as it fixes some of the known limitations. |
Hi @butonic, sorry for the late response. We made a copy of the data from the production server experiencing the problem to a test server where search_lucene used to work. The result of the data migration: search_lucene no longer worked. I then applied all the file modifications from pull request #1 , unfortunately to no avail. Upon removing the |
The saga continues: The issue appears to be related to how
Right now it seems
After clearing the |
I solved this issue in a different way. I added to the config/config.php following:
This let remain your systemwide Zend Framework intact without interfering with owncloud's own copy. |
Hi, just an update: we tried the changes from pull request #1, but they didn't fix the problem with files not getting indexed. Are there any logs we can supply so we can track down the cause and help find a possible fix? |
On 7.0.4 I am still hit by this bug:
Note that I am on shared hosting, so I cannot touch Searching has never worked for me. Sometimes, when I try it again, I get a message claiming indexing is going on, but nothing ever really seems to happen. |
@butonic What do you think? |
should be fixed with OC8, which contains search_lucene v0.6 |
Expected behaviour
Entering a string in the search bar returns filenames and files containing the provided string. Index files are created in /var/www/owncloud/data/username/lucene_index/
Actual behaviour
In the file list only files containing the string in their filename change background like when users hover the cursor over the file's row. No search results appear. When Full Text Search is disables filenames get returned. No index files are created in /var/www/owncloud/data/username/lucene_index/, only a read.lock.file exists. No records exist in the oc_lucene_status table.
Steps to reproduce
Created multiple user accounts, toggled Full Text search on and off. Entered strings appearing in stored text files into search box as well as strings matching filename.
Server configuration:
Client configuration
Browsers: Mozilla Firefox, Google Chrome, Safari (Xubuntu and Mac OS X), untested on Windows
Activated apps:
Logs
Web server error log
IP addresses and domain name replaced.
Owncloud log
When setting cron method to AJAX, the entries below are triggered by entering a search term while Full Text Search is enabled. Essentially the same errors as in the web server error log.
Manual cron execution like I encountered in ticket #3 yields the following output:
Possibly related to:
Issue #3 Class 'Zend_Search_Lucene_Document' not found
I'm at wit's end here, though that may be the end of the week talking. Any input, targeted questions, advice or remarks are appreciated.
Best regards,
Matthias
The text was updated successfully, but these errors were encountered: