nextcloud / nextcloud/fulltextsearch
Your ElasticSearchPlatform is not configured properly
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hello all,
I recently installed ElasticSearch for Nextcloud, but it doesn't work properly, my server's OS is Ubuntu + Nextcloud19.1, and issue is:
root@steven:/var/www/html# sudo -u www-data php ./nextcloud/occ fulltextsearch:test
.Testing your current setup:
Creating mocked content provider. ok
Testing mocked provider: get indexable documents. (2 items) ok
Loading search platform. (Elasticsearch) ok
Testing search platform. ok
Locking process ok
Removing test. fail
Error detected, unlocking process ok
In ConfigService.php line 144:
Your ElasticSearchPlatform is not configured properly
root@steven:/var/www/html# sudo -u www-data php ./nextcloud/occ fulltextsearch:check Full text search 1.4.2
-
Search Platform:
Elasticsearch 1.5.2
{
"elastic_host": [
"http://127.0.0.1:9200"
],
"elastic_index": "",
"fields_limit": "10000",
"es_ver_below66": "0",
"analyzer_tokenizer": ""
} -
Content Providers:
Files 1.4.3
{
"files_local": "1",
"files_external": "1",
"files_group_folders": "0",
"files_encrypted": "0",
"files_federated": "0",
"files_size": "20",
"files_pdf": "0",
"files_office": "0",
"files_image": "0",
"files_audio": "0"
}
Thanks!
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 by reproducing the failure with the occ fulltextsearch:test command and inspect ConfigService.php around line 144, using the fulltextsearch:check configuration shown in the report. Determine why the Elasticsearch platform fails while removing the test index; done means the test completes without the configuration error and the relevant behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100