Getting Data In

Product Timestamp Issue: no existing datetime.xml in $SPLUNK_HOME/etc

erb_spuser
New Member

for the Action Advisory: Product Timestamp Issue (https://docs.splunk.com/Documentation/Splunk/latest/ReleaseNotes/FixDatetimexml2020), we have downloaded an updated version of datetime.xml and tried but failed to apply it to my Splunk platform instances since we couldn't find any existing datetime.xml in $SPLUNK_HOME/etc. Could anyone advise and help. Appreciated!

-bash-4.2$ cd $SPLUNK_HOME/etc/
-bash-4.2$ ls datetime
ls: cannot access datetime: No such file or directory
-bash-4.2$ su
Password:
[root@splunk01 etc]# pwd
/etc
[root@splunk01 etc]# ls datetime
ls: cannot access datetime: No such file or directory
[root@splunk01 etc]#

Splunk Enterprise Server 7.2.8
Linux, 62.64 GB Physical Memory, 16 CPU Cores
Mode: Standalone

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The command ls datetime will always fail to find a file called datetime.xml since it's looking for the wrong name ('datetime'). Try ls datetime.xml or find $SPLUNK_HOME -name datetime.xml.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

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

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...