Splunk Search

Distributed Search times out when trying to add a peer

yazapage
Explorer

I get the following error after I add a search peer - times out. The port is open in our firewall & sending to an internal search head.

ERROR KeyManagerLocalhost - Error while sending public key to search peer https://172.18.4
8.146:4351: Connect timed out.

Is there something other than port 4351 I need to set up somewhere? I can add a search peer within the firewall wtih no issues.

Tags (2)
0 Karma

yazapage
Explorer

Thanks - I believe we only have inbound traffic allowed. I will check with my firwall team to confirm

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

I don't know what you mean when you say "sending to an internal search head", but that port is the port on the search peer/indexer, and as such, the firewall must allow TCP connections outbound from the search head to that port on the indexer. A timeout suggests that the firewall in fact is not allowing the required traffic.

0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...