Deployment Architecture

Splunk Captain transfer issue

nandha_2
Engager

Hi there,

I have three search clusters SH1, SH2 and SH3. I did the upgrade from 6.5.3 to 6.6.3. The upgrade is successful. Before the upgrade SH2 was a captain, after upgrade SH3 is the new captain. So, when I try to transfer it says

Failed to proxy call to member https://8089. ERROR: Invalid FROM mgmt_uri in transfer captaincy request err="Deserialization failed. Could not find expected key 'from_mgmt_uri'" The CLI/REST call needs to be run/hit on/the current captain, not the receiving node

Please advice.

Tags (1)
0 Karma

jaracan
Communicator

Hi,

You can run this command first on any SHC members:
/opt/splunk/bin/splunk show shcluster-status

Take note of the mgmt_uri of the SHC member you wanted. (if its IP address, use IP, if its FQDN, use FQDN)

Transfer Captaincy

/opt/splunk/bin/splunk transfer shcluster-captain -mgmt_uri https://<mgmt_uri>:8089

0 Karma

mdsnmss
SplunkTrust
SplunkTrust

It looks like the issue is where the command is run from. Are you attempting to run the captain transfer command from SH2? Try running this from SH3/the current captain:

splunk transfer shcluster-captain -mgmt_uri <desired-captain-uri>:8089 -auth <username>:<password>
0 Karma
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!

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...