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!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...