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 2022 2023 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 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Epics Archiver not pushing to STS? |
From: | Jeong Han Lee via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Manoussakis, Adamandios" <manoussakis1 at llnl.gov> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Tue, 1 Dec 2020 17:13:27 -0800 |
Ah thanks Han I see the services running now with the status script when using sudo. Also I seemed to have stumbled into the solution, the clock on the PXIe was set one hour ahead of my laptop. Apparently the archiver will throw out data that is not close enough to its clock. Does anyone know what the margin is between timestamps before the archiver will not archive the data?
Thanks for all your help as always!
From: Jeong Han Lee <citadel.lee at gmail.com>
Sent: Monday, November 30, 2020 8:28 PM
To: Manoussakis, Adamandios <manoussakis1 at llnl.gov>
Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: Re: Epics Archiver not pushing to STS?
Hi,
You may check the storage status via
bash /opt/epicsarchiverap/archappl.bash storage
Sorry for the typo in the argument.
Best,
Han
On Mon, Nov 30, 2020 at 8:15 PM Jeong Han Lee <citadel.lee at gmail.com> wrote:
HTH,
Han
On Mon, Nov 30, 2020 at 5:39 PM Manoussakis, Adamandios via Tech-talk <tech-talk at aps.anl.gov> wrote:
Hello All,
I have been successful in getting the epics archiver appliance to archive PVs that are running in soft IOCs locally on the same machine as the archiver. But now I tried to archive an IOC that is running on a subnet 192.168.40.x and it is says its connected/archiving but it never pushes to STS. It does show the details from the record for caLab:dmm shown below, which seems like its able to read from it. Settings for archiver appliance.xml below and also the archappl.conf environment variables set for the subnet to be seen. I am able to also use caget through cmdline to get values from caLab:dmm and CSStudio is able to monitor them but the archiver doesn’t seem to be actually saving the data.
<appliances>
<appliance>
<identity>appliance0</identity>
<cluster_inetport>localhost:16670</cluster_inetport>
<mgmt_url>http://localhost:17665/mgmt/bpl</mgmt_url>
<engine_url>http://localhost:17666/engine/bpl</engine_url>
<etl_url>http://localhost:17667/etl/bpl</etl_url>
<retrieval_url>http://localhost:17668/retrieval/bpl</retrieval_url>
<data_retrieval_url>http://localhost:17668/retrieval</data_retrieval_url>
</appliance>
</appliances>
JAVA_HOME="/usr/lib/jvm/java-11-openjdk-amd64"
JAVA_OPTS="-Djava.security.egd=file:/dev/./urandom"
CATALINA_HOME="/usr/share/tomcat9"
CATALINA_OPTS="-XX:MaxMetaspaceSize=256m -Xms512m -Xmx512m -XX:+UseG1GC -ea"
ARCHAPPL_APPLIANCES="/opt/epicsarchiverap/appliances.xml"
ARCHAPPL_POLICIES="/opt/epicsarchiverap/policies.py"
ARCHAPPL_PROPERTIES_FILENAME="/opt/epicsarchiverap/archappl.properties"
ARCHAPPL_MYIDENTITY="appliance0"
ARCHAPPL_STORAGE_TOP="/arch"
ARCHAPPL_SHORT_TERM_FOLDER="/arch/sts/ArchiverStore"
ARCHAPPL_MEDIUM_TERM_FOLDER="/arch/mts/ArchiverStore"
ARCHAPPL_LONG_TERM_FOLDER="/arch/lts/ArchiverStore"
EPICS_CA_ADDR_LIST=192.168.40.200
EPICS_CA_AUTO_ADDR_LIST=YES
caLab:dmm PV details section showing Never for STS push