Getting Data In

Error encountered for connection from src=10.100.100.137:48221. Local side shutting down

itmonitoring
Explorer

I'm seeing this error in a heavy forwarder, but I couldn't find any information as to what it could mean.

07-26-2013 14:53:59.324 -0600 ERROR TcpInputProc - Error encountered for connection from src=10.100.100.137:48221. Local side shutting down

The configuration I have is pretty simple:

Host -> HEAVY FORWARDER -> INDEXER

The error above shows up in splunkd.log in the Heavy Forwarder and no data makes it to the indexer.

What does it mean?

Tags (1)

sjohnson_splunk
Splunk Employee
Splunk Employee

First, are you expecting input from that host? If no, then I suspect that it might be something like a vulnerability scanner probing the HF.

If yes and the HF is linux, how many open files are available? (look in the splunkd.log for ulimit open files). Could be you ran out of file handles if there are a lot of forwarders connecting to the HF.

rsennett_splunk
Splunk Employee
Splunk Employee

Are there other messages earlier in the log?
You might want to take a look at this:
http://splunk-base.splunk.com/answers/43285/error-tcpinputproc-error-encountered-for-connection-from...

With Splunk... the answer is always "YES!". It just might require more regex than you're prepared for!
0 Karma

sf_user_199
Path Finder

I've seen this too occasionally with a very similar setup.

0 Karma
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

 Ready to master Kubernetes and cloud monitoring like the pros? Join Splunk’s Growth Engineering team for an ...

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...