Monitoring Splunk

Splunkd crash log - couldn't parse hash code


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)


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:

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

Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...