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  <20132014  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: channel archiver questions
From: James F Ross <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Fri, 10 May 2013 13:41:55 -0400
Hello all,
I know that this is an old system, but if anyone can give me a hand I would appreciate it.  I'm using the old (non CSS) epics channel archiver.  We've added a new detector at STAR and I need to add an engine to the archiver.  This is something I have done before two or three times, but this time when I added the new engine, it didn't work properly.

The engines for each detector write new index files each day in folders of the format <EngineTop>/<year>/<month_day>/index.  For example, TPCEngine/2013/05_10/index.  There is another folder under ~/Daemon where the main archiver files are located.  Every time I've made a new engine, these have automatically been included in the indexconfig.xml and indexupdate.xml files in ~/Daemon and the index files for each engine had a corresponding symbolic link called current_archive under <EngineTop>.  Meanwhile, the main web interface page, where a summary of all the engines are listed, doesn't show the new engine on it. The main web server is viewed via port 4610, with each individual engine on ports 4813 through 4826.  The new engine will be on port 4827. 

For this new engine, the index file isn't being written according to the same directory format, though a current_index file appears when the engine is run (it is not a symbolic link, but a regular file).   When running, I can see the engine on the web interface localhost:4827, but it does not show up on localhost:4610 with all the others.  Below are the files I've included and edited for the new engine.

1. Edited ArchiveDaemon.xml, the file used by the ArchiveDaemon.pl perl script when running the archiver to include an entry for the new engine at port 4827.
2. Wrote an index file at <EngineTop>/<engine>index.xml including all variables I wanted to archive
3. Included the engineconfig.dtd file used for all the engines I'm running in <EngineTop>
4. Changed firewall permissions to allow port 4827 to be used.

That is all I've done in the past (as far as I can remember) and it has worked.  Does anyone have any insight on where I might have missed something?  Particularly having to do with why the new engine doesn't appear in the automatically generated indexconfig.xml file, and thus allowing the index files to be written each day, and why it fails to appear on the main webpage.  I've looked all through everything and I can't find any typos.

Thanks everyone!
James



Replies:
Re: channel archiver questions James F Ross

Navigate by Date:
Prev: Re: Tektronix DPO4054B or Agilent DSO7054B? Fabian S.
Next: Re: Asyn-based TCP/VXI-11 interface to many devices Rod Nussbaumer
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Asyn-based TCP/VXI-11 interface to many devices Rod Nussbaumer
Next: Re: channel archiver questions James F Ross
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·