nextcloud / nextcloud/fulltextsearch
Unknown errors, but possibly cause a reindexing every container restart
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
This is after nextcloud aio's previous latest update, hoped that it would be fixed this update, no change, and I think full text search went from Elasticsearch 26 to 28? had to do something manually to get to 28, can't remember what.
The reindexing seems to go okay, but it hits 2 of these errors:
2026-07-08T02:22:35.199315303Z ┌─ Errors ────
2026-07-08T02:22:35.199317123Z │ Error: 1/1
2026-07-08T02:22:35.199318944Z │ Index: files:684154
2026-07-08T02:22:35.199320798Z │ Exception: OCA\FullTextSearch_Elasticsearch\Vendor\Elastic\Elasticsearch\Exception\ClientResponseException
2026-07-08T02:22:35.199322908Z │ Message: unknown error
Nothing in fulltextsearch container log at this timestamp to indicate what happened. how can I figure this out?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the fulltextsearch container logs around the reported 2026-07-08T02:22:35Z error and compare them with the Elasticsearch logs for index files:684154. Check the reported Elasticsearch version change from 26 to 28 and the restart-triggered reindexing behavior. Done means identifying the cause of the unknown error and determining whether it causes unnecessary reindexing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100