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!

Introducing Ingest Actions: Filter, Mask, Route, Repeat

WATCH NOW Ingest Actions (IA) is the best new way to easily filter, mask and route your data in Splunk® ...

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...