Installing the Full text search - Bookmarks app and re-indexing breaks full text search

[DecaTec]

I have set up the full text search with the following apps (on Nextcloud 14.0.1):

• Full text search - Files (1.0.1)
• Full text search - Files - Tesseract OCR (1.0.0)
• Full text search (1.0.1)
• Full text search - Elasticsearch Platform (1.0.1)

Everything was working fine. Then I installed the Bookmarks app from the Nextcloud app store and created some (~100) bookmarks. After that, I also installed the app Full text search - Bookmarks (1.0.1) as it might be a good addition to existing search functions.

I made a re-indexing of the search index by: sudo -u www-data php /var/www/nextcloud/occ fulltextsearch:reset and sudo -u www-data php /var/www/nextcloud/occ fulltextsearch:index

After re-indexing, the whole full text search seems to be broken:

• On the Files app, ony the standard Nextcloud search is available now.
• When enabling the option "Navigation Icon" in the full text search admin UI, I'm able to use the full text search again, but it only yields results from bookmarks - I can't find any files or file contents.
• Searching by command line (occ) also yields no results from files/file contents.

No entries are generated in the Nextcloud log file.

Disabling and removing the Full text search - Bookmarks app and re-indexing does not seem to help, the full text search seems to be not available anymore.

Any ideas what's the problem here?

[ArtificialOwl]

can you paste the result of ./occ fulltextsearch:check

[DecaTec]

Well, it turned out, that it's not the Full text search - Bookmarks app to blame here. Just when I enabled the app and recreated the search index, some pictures were uploaded to the cloud. One of them was a photograph of startrails. The app which caused the problem here was the Full text search - Tesseract app: It tried to recognize characters on the picture and passed out after a few minutes. Because bookmarks are indexed first, the search index obviously only contained the bookmaks and not the files.

Sorry, my bad.

On the other hand: Why the indexing is cancelled when some file cannot be indexed (there was an error message "force abort")? In my opinion, the file causing the problem should just be skipped - the indexing should not be cancelled at once.