I am getting this message below days after I applied the datetime.xml file replacement patch.
"File Integrity checks found 1 files that did not match the system-provided manifest. Review the list of problems reported by the InstalledFileHashChecker in splunkd.log File Integrity Check View ; potentially restore files from installation media, change practices to avoid changing files, or work with support to identify the problem."
I read through the release notes with the understanding that this message should be disregarded and I would disappear. However it seems to come back every time Splunk is restarted. I the only to clear this message is to download and upgrade to a pre-patched version of Splunk?
Officially, the answer is to just ignore the error and/or upgrade to a patched version. Unofficially, you could update the manifest yourself.
To clear this error, you’ll have to update the manifest file (name varies depending on splunk version) at:
You’ll want to back up the manifest, then update the line with datetime.xml with the latest sha256 hash. If you make the changes exactly as prescribed in the article, adding just the four characters specified, your new file’s hash will look like this:
f 444 splunk splunk splunk/etc/datetime.xml f2901c888ad87ac54f6d8274cdb1ec26edb5e802f71dd72a9ffa384a935692f6
But, if you want to be sure, you should be able to run sha256sum to view the hash after you update your file:
...$ sha256sum /opt/splunk/etc/datetime.xml f2901c888ad87ac54f6d8274cdb1ec26edb5e802f71dd72a9ffa384a935692f6 /opt/splunk/etc/datetime.xml
After restarting Splunk, Splunk will validate the file and since the hash in the manifest will match the hash of the file on-disk, the error will disappear.
The release notes say the message will disappear after you upgrade to a version that contains the fix. Until then, you can safely ignore the message.