Installation

Error on indexers: "ERROR ProcessDispatchedSearch - PROCESS_SEARCH - Error opening "": No such file or directory"

the_wolverine
Champion

I'm seeing tens of thousands of the following ERROR being reported by my indexers.

03-13-2014 20:37:51.925 +0000 ERROR ProcessDispatchedSearch - PROCESS_SEARCH - Error opening "": No such file or directory
Labels (1)
0 Karma
1 Solution

the_wolverine
Champion

According to Splunk Support, this is a bug due to upgrading from version 4.3.x. There is no information whatsoever about what the negative ramifications are due to this bug but our users have reported inconsistent search results while this ERROR was occurring.

http://docs.splunk.com/Documentation/Splunk/5.0.5/ReleaseNotes/5.0.5
"After upgrade from 4.3.x, splunkd.log is reporting a lot of ERROR ProcessDispatchedSearch - PROCESS_SEARCH - Error opening "": No such file or directory. (SPL-63237)""

And support indicates that this is benign so can be ignored.

View solution in original post

alanwill
Explorer

From what I understand from Splunk Support, this is a known and benign error. There's no fix ready at the moment but it can be safely ignored.

0 Karma

tugnet
Explorer

hi!

I got single search head and two indexers, was 5.0.4 is now 6.1.1 and seeing lots of those entries. Got ntpd running on all of my splunk servers, so time seems to be ok.

Has anyone got an idea how to debug or solve this issue?

0 Karma

alanwill
Explorer

I'm seeing a number of these errors in a fresh Splunk 6 instance so maybe not only related to an upgrade.

0 Karma

the_wolverine
Champion

Thanks somesoni2, but we are not having ntp issues. Support tells us this is a bug.

0 Karma

ben_leung
Builder

Should this log message been fixed by now in version 6?

0 Karma

the_wolverine
Champion

Don't even know -- they told us to just suppress the ERROR which isn't helpful in telling us whether this this is a legitimate issue we should be concerned about or not.....

0 Karma

the_wolverine
Champion

According to Splunk Support, this is a bug due to upgrading from version 4.3.x. There is no information whatsoever about what the negative ramifications are due to this bug but our users have reported inconsistent search results while this ERROR was occurring.

http://docs.splunk.com/Documentation/Splunk/5.0.5/ReleaseNotes/5.0.5
"After upgrade from 4.3.x, splunkd.log is reporting a lot of ERROR ProcessDispatchedSearch - PROCESS_SEARCH - Error opening "": No such file or directory. (SPL-63237)""

And support indicates that this is benign so can be ignored.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...