Running the TVS

Thomas D. Uram turam at mcs.anl.gov
Wed May 12 16:59:38 CDT 2004


Here are details about how the TVS is being run these days, so everyone
has the knowledge and can restart it if necessary.  The words below are
contained in a file in vv2:/disks/space0/TVS/RUNNING.

Running the TVS
----------------

The TVS is running on the machine vv2 (aka ag-dev).  It is
run from the directory /disks/space0/TVS by executing

   ./StartServer

You may be prompted for your password, subject to
the sudo rules.  If you're only concerned with getting
the server started, you don't have to read further than
the following Caveat:

Caveat: If the venue server dies in an unfavorable manner,
the Transitional.dat file that contains the venues may
be corrupted.  I haven't constructed a good way to deal with
this problem yet. I've been trying to keep a reasonable copy
in /disks/space0/TVS/TVS/AccessGrid212/bin/backup.

More details
------------
StartServer changes to /disks/space0/TVS/TVS/AccessGrid212/bin
and starts the RunVenueServer.py script in
the background using nohup.  You can, therefore, see
the output from the process in the file nohup.out.

The RunVenueServer.py script wraps the VenueServer.py
execution, restarting it if it dies or if one of its
server checks fails.  The checks include the SOAP server,
the event service, and the text service.  A log of this
activity is located in
/disks/space0/TVS/TVS/AccessGrid212/bin/RunVenueServer.log,
including uptimes.

RunVenueServer.py also generates a Statistics.csv file which includes
details about the execution, including memory use, open files,
number of threads, and cpu util.

If the server is restarted, the 'Report' script is executed,
which currently mails details to the AG team.

Stopping the server
-------------------
The server can be stoppped with the StopServer script.  This will
kill the RunVenueServer.py script first, then try to shut the
venue server down nicely, then terminate the server if necessary.







More information about the ag-dev mailing list