This page last changed on May 28, 2008 by chuckp.
How to Fix - Pipeline II
Owned by: Tony Johnson and Dan Flath
Pipeline-II servers (PROD and DEV) are now running under account glast on glastlnx12, and glastlnx07 respectively, and cron jobs are set up to start the servers after a reboot or crash at:
Test and Fix
1. Restarting an Unresponsive Server
The Pipeline-II production server (PROD) is now running under account glast on glastlnx12, and a cron job is set up
to start the server after a reboot or crash at: ~glast/pipeline-II/prod
- To Test: Check if the server is running by entering from the command line: ping glastlnx12.slac.stanford.edu
Note: If jobs are not starting as expected (see Pipeline II monitor), the server may need restarting even though it
responds to pings and other requests. (If you wish to perform additional tests, refer to the Pipeline II User's Guide.)
- To Fix: The prod server runs on glastlnx12. Do not attempt to start it elsewhere.
Only one version of the PROD pipeline can be run at a time; if a version is already running, you need to stop it
before you can restart it.
Stopping the server. If the server stops working correctly, try shutting it down as follows:
cd ~glast/pipeline-II/prod
./pipeline shutdown
If the prod server doesn't respond to a shutdown command, it can be terminated by doing:
cd ~glast/pipeline-II/prod
./stop
To start the prod server:
cd ~glast/pipeline-II/prod
./start
|
Server Properties
Property |
Default |
Prod |
mail.url |
pop3s://pipeline:xxxxxxx@exch-roam.slac.stanford.edu/ |
|
mail.from |
pipeline-dev@slac.stanford.edu |
pipeline-prod@slac.stanford.edu |
mail.to |
pipeline@slac.stanford.edu |
|
mail.error |
tonyj@slac.stanford.edu |
|
pipeline.work |
/nfs/farm/g/glast/u15/pipeline-II |
/nfs/farm/g/glast/u15/pipeline-II/prod/ |
python.cachedir |
|
/u1/tmp/pipeline-II/prod/cachedir |
file.store |
|
/nfs/farm/g/glast/u15/pipeline-II/fileStore |
db.alias |
|
PROD |
|