RE: Archiver Appliance Wrong last event timestamp

[Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov>]

Thanks Murali, the FAQ page totally explains it but unfortunately that is not the situation. When the DST began we manually set the time zone on all our Linux systems, as I said archiving data is working perfectly with correct time stamp which is what the FAQ page is saying, but the last event is always 1 hour behind with correct minutes and seconds. My PC, AA server and the IOC server are all synchronized with the same correct time zone configuration. I installed a local version of AA on my PC archiving the same PV and I got the same behavior on the last event.

 

We never looked into this but the IOC stats module shows the time zone as “CUS::360:” followed by start and end time stamps for the DST. I found this thread https://epics.anl.gov/tech-talk/2003/msg00330.php which explains how it works so the correct time zone should be something like this: “EEST::180:”, I set it manually in the IOC but still wrong last event.

 

I realize this might not be an EPICS or AA issue, right now we are troubleshooting the issue from our NTP servers’ side.

 

Thanks!

Abdalla.

 

From: Tech-talk [mailto:tech-talk-bounces at aps.anl.gov] On Behalf Of Shankar, Murali via Tech-talk
Sent: Wednesday, March 2, 2022 6:07 PM
To: tech-talk at aps.anl.gov
Subject: Re: Archiver Appliance Wrong last event timestamp

 

Please see question 5 in the FAQ - https://slacmshankar.github.io/epicsarchiver_docs/faq.html

EPICS Archiver Appliance - FAQ

Most deployment have four tomcat containers per appliance - one each for the engine, ETL, retrieval and mgmt components. All the logs typically are sent to arch.log or similar files in the CATALINA_HOME/logs of these containers. Log levels are typically controlled using a log4j.properties file in the TOMCAT_HOME/lib folder of these containers.

slacmshankar.github.io

 

 

Hope that helps.

 

Regards,

Murali