Deployment Architecture

Indexer shows multiple CLOSE_WAIT sessions on 9997 with forwarders.

sgrey007
New Member

This is probably a follow up to the question asked 20 Mar '12, 02:49 by nebel.
ERROR TcpInputProc - Error encountered for connection
In the process of adding a number of new forwarders to our recently upgraded 5.0.2 (forwarders are still at 4.3.4) we noticed the same messages in splunkd.log on two of 5 indexers.
Further we see in netstat -a, numerous CLOSE_WAIT sessions with many forwarders new and old, forwarders, in some case multiple sessions to a forwarder.
The questions are, what causes it, and are there Splunk recommended TCP tweaks for Linux (CentOS/Redhat/Ubuntu) to resolve this system problem?

0 Karma

ekost
Splunk Employee
Splunk Employee

The symptoms you're describing are similar to a recent post here.

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!

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...