No alive nodes. All the 1 nodes seem to be down. in fulltextsearch:reset but fulltextsearch:stop is working

[cdhermann]

As described in nextcloud/all-in-one#4481 my Nextcloud logs are flooded with error messages like Retry 0: cURL error 6: Could not resolve host: nextcloud-aio-fulltextsearch (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://elastic:XXX@nextcloud-aio-fulltextsearch:9200/nextcloud-aio/_search?from=0&size=5&_source_excludes=content.

BUT, the search itself works perfectly fine.

I followed the instructions on nextcloud/all-in-one#2509 to reset the Elasticsearch container. Unfortunately, the command php occ fulltextsearch:reset gives the following error

# sudo docker exec --user www-data -it nextcloud-aio-nextcloud bash
0aed8be8812d:/var/www/html$ php occ fulltextsearch:stop
stopping all running indexes
0aed8be8812d:/var/www/html$ php occ fulltextsearch:reset
WARNING! You are about to reset your indexed documents:
- provider: ALL
- collection: ALL

Do you really want to reset your indexed documents ? (y/N) y

WARNING! This operation is not reversible.
Please confirm this destructive operation by typing 'reset ALL ALL': reset ALL ALL

In SimpleNodePool.php line 77:

  No alive nodes. All the 1 nodes seem to be down.


fulltextsearch:reset [--output [OUTPUT]] [--provider PROVIDER] [--collection COLLECTION]

The search is still working perfectly fine.

• How to make the fulltextsearch app itself believe it is working fine?
• Why is the stop command working if a follow-up reset command doesn't find any alive nodes?

[lachermeierm]

I have also had these two messages in the log file since NextCloud AIO v8.0.0 or maybe later

Update: For me the search doesn't work.

"Warning – fulltextsearch – platform seems down. we will update index next cron tick"

"Error – fulltextsearch_elasticsearch – Retry 0: cURL error 28: Failed to connect to nextcloud-aio-fulltextsearch port 9200 after 133728 ms: Couldn't connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://elastic:34f24033d69c0c6f926da89ccc316385d69f983115480922@nextcloud-aio-fulltextsearch:9200/nextcloud-aio/_doc/files%3A19974"

Messages have not disappeared with Nextcloud AIO v8.1.0 either

Debian v12.5 als Linux-Container in Proxmox v8.1.10
4 cores, 4GB ram

[karthikiyengar]

Related: nextcloud/all-in-one#4290

[HajasDS]

Elasticsearch don't like special characters in password. Try use Uppercase Lowercase and numbers. To me, it solved the All the 1 nodes seem to be down issue.

[lachermeierm]

@HajasDS
Thank you for the tip. Which password do I need to change?
I have only created one user and his password consists only of upper and lower case letters and numbers.
Elasticsearch has also worked with a complex password.
I tested it and unfortunately it didn't work.

[qudiqudi]

I'm having the same issue, discussed here: nextcloud/all-in-one#5064 (reply in thread)
So far no solution.

[Lumpiness]

I tried to install nextcloud-aio manually following the instructions https://github.com/nextcloud/all-in-one/tree/main/manual-install but I got the same error:

After googling, I found a similar issue at curl/curl#11104.

In the compose file, I set the FULLTEXTSEARCH_HOST variable to nextcloud-aio-fulltextsearch.nextcloud-aio (nextcloud-aio is the name of the network to which the containers are connected).

After that, Nextcloud was able to successfully connect to the Elasticsearch container.

[Tepitus]

To set the FULLTEXTSEARCH_HOST variable worked with me, too.

[qudiqudi]

Looks like this isn't going to work with a full AIO install (docker-in-docker), only with manual install.

[mlh5599]

I was able to resolve through the UI with a full AIO install.

Under Admin -> Full Text Search, append .nextcloud-aio to the end of the url in the "Address of the Servlet" setting

@nextcloud-aio-fulltextsearch.nextcloud-aio:9200

[qudiqudi]

I was able to resolve through the UI with a full AIO install.

Under Admin -> Full Text Search, append .nextcloud-aio to the end of the url in the "Address of the Servlet" setting

@nextcloud-aio-fulltextsearch.nextcloud-aio:9200

Yes, that works. Though, changes are reset with a container restart, i.e. at next update. So we really need the devs to step in here to fix it in the container definition. I PR'ed something, not sure if that is enough. Let's see.