Will an updated datetime.xml temporarily solve the Y2K timestamp issue?

[Jarougeau]

I have recently migrated to Splunk cloud and completed the necessary version upgrades to ensure we are compatible with the timestamp issue patching. However, I still have an on-prem instance of Splunk (that is still widely used by teams) that will be de-commissioned in the next few months (upon tying up loose ends with the cloud instance).

I am running version 6.6.3 on-prem. Rather than upgrade to a compatible version, can I simply update the version of datetime.xml and apply it to each on-prem Splunk server to solve the Y2K-timestamp issue?

Obviously, this would be a temporary solution - just long enough to allow me to complete the cloud migration and de-com the on-prem environment. Thanks!

[zacharychristen · Accepted solution]

Yes, you can just download or manually update the file yourself. This will require a reboot. https://docs.splunk.com/Documentation/Splunk/6.6.3/ReleaseNotes/FixDatetimexml2020#Download_an_updat...

[Jarougeau]

Thank you. I have multiple servers in my Splunk environment, i.e., search heads, license master, cluster master, etc., do I need to update the datetime.xml in each of them, or just one specific?

[gdaly_splunk]

It requires a service restart not a reboot.

We will be releasing specific instruction videos on methods of the fix soon, including step-by-step instructions.

[malmoore]

Hi @Jarougeau,

You can use the app solution in the release note to deploy the apps to distributed environments. Review the README file that comes with the app archive download for specific instructions.