- Find Answers
- :
- Splunk Administration
- :
- Deployment Architecture
- :
- Error while adding search peer to search head
- 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'm getting the below error when adding a distributed search peer to search head on CLI or GUI.
/opt/splunk/bin/splunk add search-server x.x.x.x:8089 -auth admin:password -remoteUsername admin -remotePassword password
Invalid action for this internal handler (handler: distsearch-peer, supported: list|edit|remove|_reload|new|disable|enable|doc, wanted: create).
i'm able to connect to the indexer server via nc and there are no network or firewall blocks.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the help.
The problem was with the permissions on the trusted.pem, changing ownership and giving it to app account solved the error.
It was not showing any errors in splunkd.log on SH or on the indexer when adding the peer. It was throwing error at splunk startup on SH, which made it a little confusing.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the help.
The problem was with the permissions on the trusted.pem, changing ownership and giving it to app account solved the error.
It was not showing any errors in splunkd.log on SH or on the indexer when adding the peer. It was throwing error at splunk startup on SH, which made it a little confusing.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am facing the same issue, can you please explain this in detail:
"changing ownership and giving it to app account"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just making sure, are you running this command on search head? If so, can you see any error or warning messages in splunkd.log when trying to add search to search head?
Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...
Preparing your Splunk Environment for OpenSSL3
Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector
