SCSChannelArchiver < DaqSlowControl

You are here: Hades Wiki>DaqSlowControl Web>HadesDaqDocumentation>DetectorControlSystem>SCSChannelArchiver (27 Nov 2018, PeterZumbruch) (raw view)EditAttach
<!--
   * Set ALLOWTOPICCHANGE = Main.HadesDaqSlowControlGroup
-->
<!--           
   * Style shortcuts - bold green code          
      * Set BOLDGREENCODE =<code style="color:#008000;font-weight:bold;background-color:#f4f4f4;margin:auto;padding-left:1ex;padding-right:1ex;">          
      * Set BGC =%BOLDGREENCODE%           
      * Set ENDBGC =</code>          
      * Set BGCSPAN =<span><code style="color:#008000;font-weight:bold;background-color:#f4f4f4;margin:auto;padding-left:1ex;padding-right:1ex;">          
      * Set ENDBGCSPAN =</code></span>          
      * Set BGCDIV =<div style="background-color:#f4f4f4;padding:0.5ex;border:thin solid #808080;margin:0.5ex;padding-left:1ex;padding-right:1ex"> <code  style="color:#008000;font-weight:bold">          
      * Set ENDBGCDIV =</code></div>                  
   * Style shortcuts - small caps (larger) bold          
      * Set SCB =<span style="font-style:italic;font-variant:small-caps;">
      * Set SCE =</span>
      * Set SCLB =<span style="font-style:italic;font-variant:small-caps;font-size:larger;">
      * Set SCLE =</span>
-->
---+!! _Channel Archiver_
%TOC%

---++ Introduction
The channel archiver is usually running on lxg0434 visible to the GSI LAN

---++ Manuals

   * Channel Archiver Manual  
      * online: http://ics-web.sns.ornl.gov/kasemir/archiver/manual.pdf %ICON{"pdf"}%
      * local: [[%ATTACHURL%/ChannelArchiverManual.pdf][ChannelArchiverManual.pdf %ICON{"pdf"}%]]

---++ Sources
---+++ CVS
<ol>
   $ CVS repository : ==:ext:scs@lx-pool.gsi.de:/misc/hadesprojects/slowcontrol/cvsroot==
   $ CVS module : ==EPICS/tools/Archiver==
</ol>

---+++ Tarball (Jan 25, 2013)
<ol>
   $ CVS tarball : [[%ATTACHURL%/Archiver.tar.bz2][Archiver.tar.bz2]]
</ol>

---+++ Changes / Editing
<ol>
   The production directory of the Archiver configuration is at: %BR%
   * ==~scs/epics_apps/Archiver/config==

   Here you will find several ==*.cfg== configuration files -- for the syntax have a look at the [[#manual][manual]] -- with the easier (?) to edit pure ASCII Ansatz:
   * ==hadesArchive.cfg== %BR%
     The main configuration file including all the other files as groups, and optionally having also ordinary config entries
   * several task/detector related ==*.cfg==
</ol>

---+++ Creating the XML code
<ol>
    %BGCDIV%
      cd ~scs/epics_apps/Archiver/config && %BR%
      !ConvertEngineConfig.pl -o !hadesArchive.xml !hadesArchive.cfg
    %ENDBGCDIV%
</ol>

---++ Operation
---+++ Starting the Channel Archiver Engine on lxg0434

Since the data is stored on a local disk of ==lxg0434== this service is bound to this machine, but can be easily transfered since besides those data directories everything else is global to GSI.

<ol>
---++++ via crontab

   A crontab job of user ==scs== calling ==~/epics_apps/Archiver/config/startEngine.crontab.sh== is set up, which is called on reboot.
   * crontab entry:
      * ==@reboot /u/scs/epics_apps/Archvier/config/startEngine.crontab.sh > /tmp/archiver.crontab.start 2>&1==
   * To change the beamtime, edit the content of the ==startEngine.crontab.sh== file.
</ol>

<ol>
---++++ by Hand

<ol>
   * login%BR%
    %BGCDIV%
       ssh scs@lxg0434
    %ENDBGCDIV%
   * start engine %BR%
     Two alternatives are possible:
      1. as if crontab would have done it (recommended) %BR%
         (only possible on a pure start, use the other alternative if you have changed the configuration on a running system !) %BR%
       %BGCDIV%
          /u/scs/epics_apps/Archvier/config/startEngine.crontab.sh > /tmp/archiver.crontab.start 2>&1
       %ENDBGCDIV%
      2. every option possible %BR%
         * starting from beginning %BR%
          %BGCDIV%
             cd ~/epics_apps/Archiver/config/ %BR%
             engine.sh start [beamTime,default:beamOff] 
          %ENDBGCDIV%
         * restarting after e.g. config changes  %BR%
          %BGCDIV%
             cd ~/epics_apps/Archiver/config/ %BR%
             engine.sh restart/force-reload [beamTime,default:beamOff] 
          %ENDBGCDIV%
   * check whether it is running: %BR%
    %BGCDIV%
     ps x
    %ENDBGCDIV%
   * look for successful running job, e.g. 
    %BGCDIV%
        27898 pts/1 Sl 0:00 !ArchiveEngine -log %SCB%&lt;Log Dir&gt;/&lt;Beam Time&gt;%SCE%/Index.log -description "Hades Archive" %SCB%&lt;Config Dir&gt;%SCE%/hadesArchive.xml -port %SCB%&lt;Port&gt;%SCE%
    %ENDBGCDIV%

  *Note* : the system produces a lock-file when active and removes it on exit. Incorrect program termination causes the lock-file to stay, that will prevent the data engine from starting next time. %BR%
  __NEW__ : Taken care by ==engine.sh== script on startup, which checks for zombie files and removes them 
</ol>
---
</ol>


---+++ Starting the Channel Archiver Data Server on lxg0434

<ol>
---++++ Introduction / Settings

 The current Channel Archiver Data Server ( _StandAloneDataServer_ ) provides the data taken by the archiver and provides them via RPCXML to clients via a web server.
 It can be accessed via ==http://lxg0434.gsi.de:%SCB%&lt;Port&gt;\RPC2==.%BR%
 It initiates by reading in the file ==abyss.conf== which provides the assignments of the ethernet port number to the corresponding archives 
 and executes for each pair a Stand Alone Data Server - since the abyss server is used only one archiv per server service is allowed, so we have to call multiple server/port. %BR%

 The current (-- Main.PeterZumbruch - 31 May 2012) settings are:

 | *Archive* | *Port* | *comment* | *Access* | 
 |  apr12    | 8080 |  _current_  | http://lxg0434.gsi.de:8080\RPC2 | 
 |  jul12    | 8081 |  _future_   | http://lxg0434.gsi.de:8081\RPC2 | 
 |  beamOff  | 8090 |  _default_  | http://lxg0434.gsi.de:8090\RPC2 | 
</ol>
<ol>
---++++ via crontab

   A crontab job of user ==scs== calling ==~/epics_apps/Archiver/StandAloneServer/startServer.crontab.sh== is set up, which is called on reboot.
   * crontab entry:
      * ==@reboot sleep 60 && /u/scs/epics_apps/Archvier/StandAloneServer/startServer.crontab.sh > /tmp/archiver.dataServer.crontab.start 2>&1==
   * To change the beamtime, edit the content of the ==startServer.crontab.sh== file.
</ol>

<ol>
---++++ by Hand

<ol>
   * login%BR%
    %BGCDIV%
       ssh scs@lxg0434
    %ENDBGCDIV%
   * start engine %BR%
     Two alternatives are possible:
      * as if crontab would have done it (recommended) %BR%
       %BGCDIV%
          /u/scs/epics_apps/Archvier/StandAloneServer/startServer.crontab.sh > /tmp/archiver.dataServer.crontab.start 2>&1
       %ENDBGCDIV%
      * everything option possible %BR%
       %BGCDIV%
          cd ~/epics_apps/Archiver/StandAloneServer %BR%
          multipleDataServer.sh [start]  
       %ENDBGCDIV%
   * check whether it is running: %BR%
    %BGCDIV%
     ps x
    %ENDBGCDIV%
   * look for successful running job, e.g. 
    %BGCDIV%
        !ArchiveDataServerStandalone /u/scs/epics_apps/Archiver/StandAloneServer/abyss.%SCB%&lt;Beam Time&gt;%SCE%.conf %SCB%&lt;Data Dir&gt;%SCE%/archiver/%SCB%&lt;Beam Time&gt;%SCE%/Index
    %ENDBGCDIV%
</ol>
---
</ol>

---
</ol>

---++ Backup
At the moment (26 Apr 2016) the file base channel archiver stores its data to ==scs@lxhadeb06:/data01/scs/archiver==.%BR%
Therefore two ways of backup are:
   1. daily, ==cron== based ==rsync== on ==lxhadeb07== retrieving the data from ==lxhadeb06:/data01/scs== to ==lxhadeb07:/data01/scs==
      * ==crontab== entry: %BGCDIV%@daily rsync -aAX scs@lxhadeb06:/data01/scs/ /data01/scs%ENDBGCDIV%
   1. ==TSM/DSM== backup of ==lxhadeb06:/data01/scs==
      * q.v. &rArr; https://wiki.gsi.de/Linux/TsmBackup
      * in preparation

---
-- Main.PeterZumbruch - 26 Apr 2016
Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
bz2	Archiver.tar.bz2	manage	28.4 K	25 Jan 2013 - 10:42	PeterZumbruch	setup data, status 25 Jan 2013
pdf	ChannelArchiverManual.pdf	manage	1130.8 K	04 Jun 2012 - 14:39	PeterZumbruch	Channel Archiver Manual
Topic revision: r7 - 27 Nov 2018, PeterZumbruch
DaqSlowControl
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)