Getting Data In

s2s negotiation failed between forwarder running host and indexers

parth995
Loves-to-Learn Lots

Using splunkforwarder-9.0.2-17e00c557dc1.x86_64 on forwarder linux box
Using splunk-9.0.4-de405f4a7979.x86_64 on indexer node.
From forwarder node I am able to telnet indexer node fine.
On forwarder node splunkd.log, I see below error for s2s negotiation failed.

 

ERROR AutoLoadBalancedConnectionStrategy [25021 TcpOutEloop] - s2s negotiation failed. response='NULL'
ERROR TcpOutputFd [25021 TcpOutEloop] - s2s negotiation failed. response='NULL'

 

Labels (1)
0 Karma

parth995
Loves-to-Learn Lots

Hey @isoutamo , May be I found the fix

I noticed inputs.conf on splunk indexer side was not having port mentioned on one of the block 

Added
"[splunktcp:<PORT>]" in $SPLUNK_BASE/etc/system/local on indexers


This fixed issue

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

can you paste your inputs.conf on indexer side and outputs.conf from UF side? Please anonymise (read: replace with xxx etc.) all data which can identified your environment and secrets!

And remove put those inside </> element on your reply!

r. Ismo

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...