Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- Error on indexers: "ERROR ProcessDispatchedSearch...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm seeing a number of these errors in a fresh Splunk 6 instance so maybe not only related to an upgrade.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks somesoni2, but we are not having ntp issues. Support tells us this is a bug.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Should this log message been fixed by now in version 6?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.....
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
