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!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...