https://community.splunk.com/t5/Monitoring-Splunk/Splunkd-crash-log-couldn-t-parse-hash-code/m-p/13314#M77 <P>The following line is found when I try to restart the stopped splunkd process:-</P> <P>05-12-2010 14:30:50.819 ERROR WordPositionData - couldn't parse hash code: </P> <P>Cannot get Splunk running again, Please advise</P> Wed, 12 May 2010 20:43:16 GMT aiwatson 2010-05-12T20:43:16Z https://community.splunk.com/t5/Monitoring-Splunk/Splunkd-crash-log-couldn-t-parse-hash-code/m-p/13314#M77 <P>The following line is found when I try to restart the stopped splunkd process:-</P> <P>05-12-2010 14:30:50.819 ERROR WordPositionData - couldn't parse hash code: </P> <P>Cannot get Splunk running again, Please advise</P> Wed, 12 May 2010 20:43:16 GMT https://community.splunk.com/t5/Monitoring-Splunk/Splunkd-crash-log-couldn-t-parse-hash-code/m-p/13314#M77 aiwatson 2010-05-12T20:43:16Z https://community.splunk.com/t5/Monitoring-Splunk/Splunkd-crash-log-couldn-t-parse-hash-code/m-p/13315#M78 <P>Usually, more information is required for investigating crashes:</P> <UL> <LI>Which version of Splunk?</LI> <LI>Which platform?</LI> <LI>What's in the crash log?</LI> </UL> <P>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: <A href="http://answers.splunk.com/questions/715/corrupt-metadata" rel="nofollow">http://answers.splunk.com/questions/715/corrupt-metadata</A></P> <P>Or, contact support and provide a splunk-diag from the instance in question for further assistance.</P> Wed, 12 May 2010 23:10:06 GMT https://community.splunk.com/t5/Monitoring-Splunk/Splunkd-crash-log-couldn-t-parse-hash-code/m-p/13315#M78 the_wolverine 2010-05-12T23:10:06Z