Monitoring Splunk

Splunk Indexer Error

abhijitnath89ax
Loves-to-Learn

We received the below error in splunkd.log on our indexer server. We are using cluster env with 6 indexers. The indexers are coming up and down

11-05-2020 07:23:03.304 +0000 ERROR TcpInputProc - Error encountered for connection from src=X.X.X.X:60116. Broken pipe
Labels (2)
0 Karma

nwuest
Path Finder

Hi @abhijitnath89ax,

After doing some researching about the error you have depicted could be related to the indexers trying to see if the others indexers/receivers are "alive" named a heartbeat function.

View solution in original post by @hliakathali_spl 

 

Would there happen to be a firewall change either in the network and/or a firewall change on the Splunk Indexers themselves that are prohibiting the connection between them?

 
We hope to hear back from you!
 
V/R,
nwuest
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!

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...

Splunk Enterprise Security: An Automated Phishing Response Workflow

Originally posted on Splunk.com.   Key takeaways  The volume of phishing emails can overwhelm even the most ...

Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...

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