Deployment Architecture

Adding a cluster peer: error Bad Request in handler clusterconfig

ekost
Splunk Employee
Splunk Employee

While adding a peer node to the cluster master, I receive the error:

Bad Request — In handler 'clusterconfig': Could not contact master. Check that the master is up, the master_uri=http://winry_dc02.orborous.net.local:8089 and secret are specified correctly

Both configurations were verified (DNS resolves and the secret is ok). What's going on?

Tags (1)

sloshburch
Ultra Champion

I had the same issue and it was not the protocol. I had to hard code the IP instead of using the DNS name of the host. This worked fine in 5.0.2 but not after a 6.0.1 upgrade.

0 Karma

DerekB
Splunk Employee
Splunk Employee

In your URI, you should use https:// not http://. If you correct that, this will work.

You can confirm this configuration on this doc page:

http://docs.splunk.com/Documentation/Splunk/latest/Indexer/Enablethepeernodes

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...