Deployment Architecture

Add cluster peer trying to reach wrong endpoint

tiagofbmm
Influencer

Hello

I am using a NFR license.
I am mounting a cluster environment in ubuntu, where my cluster master is on splunkd-port 8090
I have another ubuntu in a virtualbox running there on port 8089.

When I try to add the vbox peer to the cluster, I get this error:
Error=http client error=Connection refused, while trying to reach https://192.168.1.111:8089/services/cluster/config.

I don't understand why splunk is trying to reach for https://192.168.1.111:8089 if splunkd-port for the cluster master is 8090. Anyone?

0 Karma

tiagofbmm
Influencer

Yes I just confirmed I have both master_uri correct in the server.conf of both peers.

One note, it doesn't matter what peer I add first. The first one always works like a charm, the second one to be added makes the master show the message I noted in the question.

0 Karma

hardikJsheth
Motivator

Can you check the master_url entry in $SPLUNK_HOME/etc/system/local/server.conf file on your peer node ? You need to provide correct ip and port as per your master node configuration:

i.e
[clustering]
master_uri = https://a.b.c.d:8089
mode = slave

0 Karma
Get Updates on the Splunk Community!

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

September Community Champions: A Shoutout to Our Contributors!

As we close the books on another fantastic month, we want to take a moment to celebrate the people who are the ...