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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

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

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...