https://community.splunk.com/t5/Knowledge-Management/file-integrity-check/m-p/343519#M5127 <P>An array of issues started when I upgraded from 6.5 -&gt; 6.6 and one being that I currently have 124 files that differ from the hash within the 6.6 manifest. </P> <P><STRONG>Is there a way to update the manifest with current HASH or to accept the current changes?</STRONG></P> <P>I can manually run a sha256sum on the files and update the hash within the manifest, but I am hoping there is a quicker way.</P> <P>Thank You,<BR /> Sean</P> Mon, 31 Jul 2017 17:05:42 GMT rewritex 2017-07-31T17:05:42Z https://community.splunk.com/t5/Knowledge-Management/file-integrity-check/m-p/343519#M5127 <P>An array of issues started when I upgraded from 6.5 -&gt; 6.6 and one being that I currently have 124 files that differ from the hash within the 6.6 manifest. </P> <P><STRONG>Is there a way to update the manifest with current HASH or to accept the current changes?</STRONG></P> <P>I can manually run a sha256sum on the files and update the hash within the manifest, but I am hoping there is a quicker way.</P> <P>Thank You,<BR /> Sean</P> Mon, 31 Jul 2017 17:05:42 GMT https://community.splunk.com/t5/Knowledge-Management/file-integrity-check/m-p/343519#M5127 rewritex 2017-07-31T17:05:42Z https://community.splunk.com/t5/Knowledge-Management/file-integrity-check/m-p/343520#M5128 <P>It looks like EITHER the manifest got updated ( <CODE>$SPLUNK_HOME/*-manifest</CODE>) and the other files did not, or the other way around. Either way you have a pretty failed upgrade and I check/fix all file/directory permissions and run the installation again.</P> Mon, 31 Jul 2017 17:37:34 GMT https://community.splunk.com/t5/Knowledge-Management/file-integrity-check/m-p/343520#M5128 woodcock 2017-07-31T17:37:34Z