Archive

WHat does it mean this error regarding bundle conflicting timestamp

Explorer

Apparently splunk is behaving correctly, but sometimes using historical searches in order to reduce search time does not work. I only see in the splunkd log several similar messages like this:

ERROR DistributedBundleReplicationManager - HTTP response code 400 (HTTP/1.1 400 Bad Request). Error applying delta=/opt/splunk/var/run/searchpeers/SV19APSP027-1520781662-1520781908.delta, searchHead=SV19APSP027, prevTime=1520781662, prevChksum=13407166704320477873, curTime=1520781908, curChksum=14856987335408760282: Latest bundle has conflicting timestamp: searchHead=SV19APSP027, actual=1520

But also other messages like this, although doesn't seem to be related:

ERROR ScriptRunner - stderr from '/opt/splunk/bin/python /opt/splunk/etc/apps/search/bin/sendemail.py "resultslink=http://SV19APSP027:8000/app/search/search?q=%7Cloadjob%20rtscheduleracalasanzsearchRMD58cdfb26d24a1b7d9at152087088029688.0%20%7C%20head%201%20%7C%20tail%201&earliest=0&latest=now" "ssname=SPK0003-US-Cambio de Contraseña" "graceful=True" "triggertime=1520871180" resultsfile="/opt/splunk/var/run/splunk/dispatch/rtscheduleracalasanzsearchRMD58cdfb26d24a1b7d9at152087088029688.0/perresultalert/tmp0.csv.gz"': ERROR:root:[Errno -3] Temporary failure in name resolution while sending mail to: acalasanz@bancopromerica.com, lcastellanos@bancopromerica.com, hucles@bancopromerica.com

Tags (1)

Builder

@luis290311: were you able to fix this issue, we are seeing this on our search-heads, we are 7.2.1

Champion

What splunk version you are using?

Explorer

version of Splunk: 7.02

By the way, I will add some additional information. In the moment of the problem, in the splunk's console it appears the following message:

Dispatch command: The number of search artifacts in the dispatch directory is higher than recommended (count=32536,, warning threshold=5000) and could have an impact on search performance. Remove excess search artifacts using "splunk clean-dispatch" CLI command, and review artifact retention policies in limits.conf and saved searches.conf. You can also raise this warning threshold in limits.conf / dispatchdirwarning_size.

We followed this instructions but the same issue persists.

0 Karma