EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Archiver Appliance Wrong last event timestamp
From: Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov>
To: "Shankar, Murali" <mshankar at slac.stanford.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 3 Mar 2022 10:15:26 +0000

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

 

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

 


References:
Re: Archiver Appliance Wrong last event timestamp Shankar, Murali via Tech-talk

Navigate by Date:
Prev: Re: Timing in seq record Johnson, Andrew N. via Tech-talk
Next: RE: Timing in seq record Freddie Akeroyd - STFC UKRI via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
Navigate by Thread:
Prev: Re: Archiver Appliance Wrong last event timestamp Shankar, Murali via Tech-talk
Next: loc vs sim in Phoebus Mogamat Amien Crombie via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·