Tons of redis and elasticsearch errors without me changing anything

I’m getting crap ton of these:
Retry 0: Failed to connect to nextcloud-aio-fulltextsearch port 9200 after 8 ms: Couldn't connect to server for "http://elastic:26eb5298dadfd568f33b3e5c4825099f2229573c9d16ec8b@nextcloud-aio-fulltextsearch:9200/nextcloud-aio/_doc/files%3A647322".

and these


Redis::pconnect(): php_network_getaddresses: getaddrinfo for nextcloud-aio-redis failed: Name does not resolve at /var/www/html/lib/private/RedisFactory.php#117

Complete log here

NC AIO 8.2.1 (NC 28.0.5) running as Proxmox LXC behind Nginx Proxy Manager. This started like a week ago. Any tips? Thanks.

Hi, can you check if you are running into this? How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub

1 Like

Thanks but no, done that, got no errors, but that’s not it. It’s bad and getting worse:

Getting this from core repeatedly

Exception
Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7] could not translate host name "nextcloud-aio-database" to address: Name does not resolve
Exception thrown: Doctrine\DBAL\Exception

and this from fulltextsearch_elasticsearch

Retry 0: Failed to connect to nextcloud-aio-fulltextsearch port 9200 after 9 ms: Couldn’t connect to server for “http://elastic:26eb5298dadfd568f33b3e5c4825099f2229573c9d16ec8b@nextcloud-aio-fulltextsearch:9200/nextcloud-aio/_search?from=0&size=5&_source_excludes=content”.

this from richdocuments

ServerException


Server error: `GET https://MY.SERVER.cz/hosting/capabilities` resulted in a `502 Bad Gateway` response: <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>open (truncated...)
Failed to fetch the Collabora capabilities endpoint: Server error: `GET https://MY.SERVER.cz/hosting/capabilities` resulted in a `502 Bad Gateway` response: <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>open (truncated...)

I have even tried resetting the index to no avail. Still getting these.

The main thing in common with all of your errors is DNS resolution is not functioning in your container environment for some reason (or the referenced containers - Redis and your db one - are offline for some reason).

The AIO interface (and docker ps) shows everything as Running…

I just disabled Fulltext search. I don’t need it on this server anyway.

Based on the logs your posted it sounded like it was more than just FTS impacted though?

After disabling FTS-related stuff, errors stopped. I didn’t encounter anything broken while using my NC instance. I don’t know :-/