Meanwhile: I setup a fresh installation with Ubuntu server und Nextcloud being installed with system setup (also using snap). Added Elasticsearch - everything works as expected, i.e. search in NV returns file with search string being part of content.
I then extracted configuration data with
sudo nextcloud.occ config:list > config-list.txt
and compared the files of my two installations.
What I found was
"fulltextsearch": {
"app_navigation": "1",
"cron_err_reset": "1598114208",
"enabled": "yes",
"installed_version": "1.4.2",
"provider_indexed": "{\"deck\":\"1\",\"files\":\"1\"}",
"search_platform": "OCA\\FullTextSearch_ElasticSearch\\Platform\\ElasticSearchPlatform",
"types": ""
}
on the working server. On the failing server one line is different
"provider_indexed": "{\"deck\":\"1\"}",
I now suspect that this maybe the reason for my problems.
Deleting the NC apps and reinstalling them did not help. Re-indexing files via
sudo nextcloud.occ fulltextsearch:index --no-readline
did not help.
So I came up with what is described in Install and configure FullTextSearch + Elasticsearch using occ / command line.
But that command fails with “The file must contain a valid json array”.
I suspect that the JSON data showed there should be inside
“system”: {}
Someone here to comment on that?
Where can I find more information regarding configuration via OCC, especially search? I did see the docs on Github, but regarding search that was not as specific as required. And reading PHP code is not my business, sorry.
Greetings Wolfgang