Splunk Search

Error Logs on Splunkd (Search Head)

mldaplin
Engager

Hi,

I'm having this error logs on my search heard splunkd.

01-15-2011 00:22:06.346 WARN NetUtils - Bad select for loop rv = -2

01-17-2011 14:13:36.874 WARN DistributedBundleReplicationManager - bundle replication to 3 peer(s) took too long (35830ms), bundle file size=5960KB

These logs might also cause my search peers to not be replicated.

Regards, Marlon

Tags (2)

woodcock
Esteemed Legend

You need to do a traceroute and see if there is network latency that is causing this and if not, you need to inspect the job with the job inspector:

http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/ViewsearchjobpropertieswiththeJobInspec...

It is quite possible that your dispatch directory is too full or that there is some other OS problem that is causing writes to fail. In any case, you almost certainly will have unreliable results if your bundle replication is failing.

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...