Page History

...

• create and edit a shutdown_schedule_date <date> file:

  Code Block
  $ date > shutdown_schedule_20100909 $ vim shutdown_schedule_20100909

• the shutdown_schedule_date <date> file should look something like this (the start time should be some 10 minutes before the beginning of the outage, the stop time should be a few hours after the expected end of the outage); important: leave a blank line at the end of the file:

  Code Block
  Thu Sep 9 09:50:00 PDT 2010 Thu Sep 9 13:50:00 PDT 2010

• create a symbolic link for shutdown_schedule_date <date> as shutdown_schedule:

  Code Block
  ln -s shutdown_schedule_20100909 shutdown_schedule

• the pipeline should shutdown automagically a few minutes after the start time in the shutdown_schedule file (there is a cronjob involved, plus it can take a couple of minutes for it to go down)

• the pipeline will start again automatically after the end date specified in the shutdown_schedule file. If you want to extend the outage before the end date occurs, you can modify and save the file.

• to restart the pipeline before the outage is over, modify the end date to be before the current time and save the file, or just remove the symbolic link (leaving the shutdown_schedule_date <date> file for future reference):

  Code Block
  rm shutdown_schedule

...

• first of all, login as glast to some interactive glastlnx12 machine and go to the pipeline directory:

  Code Block
  $ ssh glast@noric $ cd ~glast/pipeline-II/prod/

• issue the pipeline ping command to find out where the pipeline is running (for PROD this is currently glastlnx12, for DEV it is currently glastlnx13, and for TEST it is currently glastlnx07)

  Code Block
  $ ./pipeline ping Pinged server version 1.3.5 running on glastlnx12.slac.stanford.edu since 2010-09-07 16:57:28.012

• ssh to the server listed (in the above example, it was glastlnx12.slac.stanford.edu) This is not strictly necessary when using the pipeline shutdown command, but it is necessary to run the start and stop scripts from the correct machine.

  Code Block
  ssh glast@glastlnx12

• move out of the way the monitor script (which will restart the pipeline whenever it doesn't find it running):

  Code Block
  $ mv monitor monitor_something_something

• shutdown the pipeline server with the shutdown command:

  Code Block
  $ ./pipeline shutdown

• perform whatever work required the outage

• restart the pipeline using the start script:

  Code Block
  $ ./start

...