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
Get Updates on the Splunk Community!

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...

State of Splunk Careers 2024: Maximizing Career Outcomes and the Continued Value of ...

For the past four years, Splunk has partnered with Enterprise Strategy Group to conduct a survey that gauges ...

Data-Driven Success: Splunk & Financial Services

Splunk streamlines the process of extracting insights from large volumes of data. In this fast-paced world, ...