Swarm - Docker image healthcheck never passes about graylog-docker

[janheise]

Hi @Nathan-Nesbitt, I have no idea about swarm - but would like to ask about some more info:
This is an existing setup that you upgrade, right? And you want to connect to an existing Elasticsearch 7.10.2?

In this case, you should specifiy the connection string to elasticsearch in your docker-compose files (https://go2docs.graylog.org/5-2/setting_up_graylog/graylog_data_node_getting_started.htm?tocpath=Setting%20up%20Graylog%7CGraylog%20Data%20Node%7C_____1)

sth. like GRAYLOG_ELASTICSEARCH_HOSTS: "http://opensearch1:9200,http://opensearch2:9201,http://opensearch3:9202"

This should at least skip the "waiting for the initial setup" step - which in your case is not necessary.

[Nathan-Nesbitt]

@janheise great workaround thank you it's back up 💯

Looks like this is still a problem tho as I won't be able to redeploy on any new machines. Let me know how I can help diagnose / narrow this down and I'll do what I can to help!

[janheise]

@Nathan-Nesbitt - I'm happy that I was able to help. As I wrote, I have no experience with swarm. With redeploy, do you mean "set up a whole new cluster from scratch" or "adding new machines to an existing cluster". As long as the MongoDB stays intact (unless, as I said, you want to start from 0) adding new machines should work out fine.

A completely new setup should work fine, too, if you use plain OpenSearch/Elasticsearch. For the DataNode, I'd have to make some tests with swarm - but with some manual pre-configuration, it should work, too.

[Nathan-Nesbitt]

@janheise Totally, I am more concerned if I need to set this up on a whole new cluster!

What would be involved with the manual configuration? :)

[janheise]

@Nathan-Nesbitt Let me reiterate: if you use plain OpenSearch for new setups nothing changes except the elasticsearch_hosts setting that is now mandatory.

First steps we undertook with the DataNode is simplifying the SSL configuration for your setups by adding a UI etc. You can also generate your own certificates and add them to the config manually and by doing so, skip the initial configuration, too. We'll probably support swarm installations etc. better in upcoming releases. 5.2 is our first release with the DataNode. I'll put "test with and support swarm" in our to-do list.

[janheise]

problem seems to be fixed