Deployment Architecture

Distributed Search Configuration

jthairu_splunk
Splunk Employee
Splunk Employee

I am trying to configure my search head to search my indexer and i keep receiving the following error:

Error while sending public key to search peer: Connect Timeout

One of the troubleshooting steps recommended was to make sure that splunkd is running with it is both on the SH and indexer.

Does anyone know what else I can try?

Thanks

Tags (1)
0 Karma

harsmarvania57
Ultra Champion

Are you able to connect Indexer management port from Search Head server?

Check using command telnet indexer 8089 if you are using linux

0 Karma

jthairu_splunk
Splunk Employee
Splunk Employee

when I run the telnet command I get the following:

telnet: indexer: Name or service not known
indexer: Unknown host

0 Karma

harsmarvania57
Ultra Champion

Ah, replace indexer with your indexer IP address so for example telnet 192.168.1.1 8089

0 Karma

harsmarvania57
Ultra Champion

Means there is communication problem between your Search Head and Indexer. Possible causes are firewall blocking, route problem etc.

0 Karma

jthairu_splunk
Splunk Employee
Splunk Employee

ok, I did that and the connection timed out

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!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...