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!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...