Monitoring Splunk

Splunkd crash log - couldn't parse hash code

aiwatson
Engager

The following line is found when I try to restart the stopped splunkd process:-

05-12-2010 14:30:50.819 ERROR WordPositionData - couldn't parse hash code:

Cannot get Splunk running again, Please advise

Tags (1)

the_wolverine
Champion

Usually, more information is required for investigating crashes:

  • Which version of Splunk?
  • Which platform?
  • What's in the crash log?

If by chance you're running 4.1x on Windows, the error most likely to points to an issue with corrupted metadata files due to a crash. The corruption of metadata files due to crash will be fixed in 4.1.4. In the meantime you could try to repair your metadata files per this answers post: http://answers.splunk.com/questions/715/corrupt-metadata

Or, contact support and provide a splunk-diag from the instance in question for further assistance.

Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...