Hi Jochen
To be honest, I'm not completely sure.
Like I said in the original post, I am setting up Graylog with an ES
cluster. Right now, I am unable to start Graylog due to the initialization
error discussed above.
I have checked the elasticsearch unicast setting, and it does seem correct.
I am able to reach ES via the configured host names from within the Graylog
docker container.
GRAYLOG_ELASTICSEARCH_NETWORK_PUBLISH_HOST: 10.0.200.100
GRAYLOG_ELASTICSEARCH_DISCOVERY_ZEN_PING_UNICAST_HOSTS:
ha-gelf-01-es:9300,ha-gelf-es-02:9300,ha-gelf-es-03:9300
GRAYLOG_ELASTICSEARCH_CLUSTER_NAME: "graylog"
GRAYLOG_IS_MASTER: "true"
Since I am not able to start Graylog, the log does not state that an error
is occuring and I have checked the unicast setting, I need to figure out
what the next course of action is going to be.
Since this began occurring after I restarted Graylog while it had a working
configuration with a graylog index created in the cluster (at least to my
knowledge), I thought of resetting Graylog back to before the index was
created.
On Friday, October 7, 2016 at 10:49:15 AM UTC+2, Jochen Schalanda wrote:
>
> Hi John,
>
> On Friday, 7 October 2016 10:43:59 UTC+2, John B wrote:
>>
>> Is there a way I can force a reset or similar (without doing a full
>> deletion)?
>>
>
> What do you want to reset exactly?
>
> Cheers,
> Jochen
>
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/3b3d58a0-2b35-491d-b056-0f1d9be62803%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
