Failure setting indexers as search peers about docker-splunk HOT 4 CLOSED

Hey @JasonConger,

I have investigated this issue and made a fix for it in the Splunk-Ansible Repo.

Seems like peering works after the fix. Note that I took out volumes and license configurations from your yaml since it is your custom resource.

from docker-splunk.

fix here: splunk/splunk-ansible#15

from docker-splunk.

Hi jdso7! Have you followed the steps for using docker run to create a defaults.yaml?

https://github.com/splunk/docker-splunk/blob/master/documentation/ADVANCED.md#defaultyml-valid-options

If you check out the advanced documentation section, or the kubernetes examples (you do not need to know.use k8s for this to be relevant):
https://github.com/splunk/docker-splunk/tree/master/test_scenarios/kubernetes, there is a walkthrough of creating this file to serve the base configs to any container in a deploy, and serving it centrally using nginx. You could also just ensure to copy it into the container when you build it, etc.

This is an inportant file to get right to ensure the options you want/need (ie. clustering, pass4SymKey, replication ports, etc)

My hunch is we just need to get your defaults.yaml sorted to match the desired environment you want to build. Do you want the indexers to be clustered, or just standalone, etc.

Try using docker run to generate one, and we can start there to ensure all the items you want globally are set and accounted for in defaults.yaml or in env variables in the container.

I think the last time I saw this error, it was because there was no Master Node and Indexer Clustering was enabled.

from docker-splunk.

Hi matthewmodestino,

Yes, I have been looking at that documentation. I've used environment variables instead of passing values in the defaults.yaml file.

It's a bit hard to understand the error from the log, even in debug.
So thank you for your hints, I'll double-check those settings.

from docker-splunk.