Splunkd crash log - couldn't parse hash code

aiwatson · ‎05-12-2010

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

the_wolverine · ‎05-12-2010

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.

Splunkd crash log - couldn't parse hash code

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.

A Four-Part Event Series: State of Observability - Where AI Meets Performance

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Build resilience for the agentic era: Join us at Splunk Go San Jose

Join the Conversation

Splunkd crash log - couldn't parse hash code

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.

A Four-Part Event Series: State of Observability - Where AI Meets Performance

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Build resilience for the agentic era: Join us at Splunk Go San Jose