Getting Data In

Splunk Forwarder not sending logs

pdash
Path Finder

I get the following error:

10-09-2013 00:28:22.177 -0600 WARN TcpOutputFd - Connect to X.X.X.X:9997 failed. No connection could be made because the target machine actively refused it.
10-09-2013 00:28:22.177 -0600 ERROR TcpOutputFd - Connection to host=X.X.X.X:9997 failed
10-09-2013 00:28:22.177 -0600 WARN TcpOutputProc - Applying quarantine to ip=X.X.X.X port=9997 _numberOfFailures=3

Also this warning was found in splunkd

PipelineComponent - MetricsManager:probeandreport() took longer than seems reasonable (11141 milliseconds) in callbackRunnerThread. Might indicate hardware or splunk limitations.

Tags (1)
0 Karma

ncsantucci
Path Finder
0 Karma

kristian_kolb
Ultra Champion

What do the logs look like on the indexer. I'm not sure that it's a connectivity problem. "Actively refused" sounds like a RST was sent by the indexer.

Running out of file descriptors?

gfuente
Motivator

Hello

Did you verified that the firewall ports are open? It seems to be a connectivity problem

Try to do a telnet from the fw to the indexer, from the command line:

telnet indexer 9997

Regards

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...