Splunk Search

Why is my search resulting in error "Streamed search execute failed because: JournalSliceDirectory: Cannot seek to 0"?

mlevsh
Builder

While running the search index=networking | timechart count on Splunk v. 6.3.3, we are getting the following error:

Streamed search execute failed because: JournalSliceDirectory: Cannot seek to 0

• What does this message mean?
• What steps should I take to troubleshoot this and what logs would give me more insight into the error (besides splunkd.log)?
• What is the possible solution?

Thank you!
Marina

0 Karma
1 Solution

mlevsh
Builder

Just an update: we opened splunk support ticket. The plan that worked was to run command $SPLUNK_HOME/bin/splunk fsck scan --all-buckets-all-indexes --v, redirect output to a file, find "corrupted" buckets in output text file, and run the splunk rebuild command on each of the buckets. When rebuild is not working, replace it with a good one from other indexer servers (searchable). This fixed the issue.

View solution in original post

mlevsh
Builder

Just an update: we opened splunk support ticket. The plan that worked was to run command $SPLUNK_HOME/bin/splunk fsck scan --all-buckets-all-indexes --v, redirect output to a file, find "corrupted" buckets in output text file, and run the splunk rebuild command on each of the buckets. When rebuild is not working, replace it with a good one from other indexer servers (searchable). This fixed the issue.

Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...