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
Get Updates on the Splunk Community!

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  &#x1f680; Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...