Channel Archiver

Introduction

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

Manuals

Sources

CVS

    CVS repository
    :ext:scs@lx-pool.gsi.de:/misc/hadesprojects/slowcontrol/cvsroot
    CVS module
    EPICS/tools/Archiver

Tarball (Jan 25, 2013)

    CVS tarball
    Archiver.tar.bz2

Changes / Editing

    The production directory of the Archiver configuration is at:
    • ~scs/epics_apps/Archiver/config

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

Creating the XML code

    cd ~scs/epics_apps/Archiver/config &&
    ConvertEngineConfig.pl -o hadesArchive.xml hadesArchive.cfg

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.

    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.

    by Hand

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

      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.
      NEW : Taken care by engine.sh script on startup, which checks for zombie files and removes them

Starting the Channel Archiver Data Server on lxg0434

    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:<Port>\RPC2.
    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.

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

    Archive PortSorted descending comment Access
    beamOff 8090 default http://lxg0434.gsi.de:8090\RPC2
    jul12 8081 future http://lxg0434.gsi.de:8081\RPC2
    apr12 8080 current http://lxg0434.gsi.de:8080\RPC2

    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.

    by Hand

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


Backup

At the moment (26 Apr 2016) the file base channel archiver stores its data to scs@lxhadeb06:/data01/scs/archiver.
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:
      @daily rsync -aAX scs@lxhadeb06:/data01/scs/ /data01/scs
  2. TSM/DSM backup of lxhadeb06:/data01/scs


-- PeterZumbruch - 26 Apr 2016
I Attachment Action Size Date Who Comment
Archiver.tar.bz2bz2 Archiver.tar.bz2 manage 28 K 2013-01-25 - 11:42 PeterZumbruch setup data, status 25 Jan 2013
ChannelArchiverManual.pdfpdf ChannelArchiverManual.pdf manage 1 MB 2012-06-04 - 16:39 PeterZumbruch Channel Archiver Manual
Topic revision: r7 - 2018-11-27, PeterZumbruch
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki Send feedback | Imprint | Privacy Policy (in German)