Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Deployment Architecture
- :
- Error in Pre-deploy check
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have 3 new splunk enterprise. 2 are acting as search heads and 1 is acting as deployer.
I have successfully made them as a cluster and can even push user and search configs but when i push app or add-ons from deployer i get below error.
Error in pre-deploy check, uri=https://x.x.x.x8089/services/shcluster/captain/kvstore-upgrade/status, status=401, error=No error
even the password is correct for deployer which is also same for both SHs.
What could be the issue here
PS: I know splunk recommend to use 3 SH and 1 deployer. I tried it as well but have same issue.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the solution.
It was Pass4symmkey issue, I had some special charaters in my pass4symmkey due to which there was a difference is passwords.
to check use below commands.
splunk btool server list shcluster --debug | grep -i pass4symmkey ( this will give you your password on spunk)
splunk show-decrypted --value 'pass4symmkey' (this will decrypt the key)
now verify the pass key it will surely be a missmatch.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the solution.
It was Pass4symmkey issue, I had some special charaters in my pass4symmkey due to which there was a difference is passwords.
to check use below commands.
splunk btool server list shcluster --debug | grep -i pass4symmkey ( this will give you your password on spunk)
splunk show-decrypted --value 'pass4symmkey' (this will decrypt the key)
now verify the pass key it will surely be a missmatch.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, thanks for your help, had similar issue due to splunk init shcluster-config, secret key wasn't correctly encrypted in server.conf apparently, as seen with help of splunk show-decrypted
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Persistent Queue at TcpOut — One of Splunk's Most Practical Features
Build resilience for the agentic era: Join us at Splunk Go San Jose
Manage Edge Processor pipelines end to end with APIs
