Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • to check the status of the pipeline server, one can use the ping function of the pipeline:
    Code Block
    
    glast@noric09 $ ./pipeline ping
    Pinged server version 1.3.5 running on glastlnx12.slac.stanford.edu since 2010-09-07 16:57:28.012
    

To stop and start the pipeline manually (if all else fails):

  • First of all, login as glast to some interactive machine and go to the pipeline directory.
    Code Block
    
    $ ssh glast@noric
    $ cd ~glast/pipeline-II/prod/
    
  • 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
    
  • restart the pipeline using the start script:
    Code Block
    
    $ ./start
    
  • move back the monitor script to its original location:
    Code Block
    
    $ mv monitor_something_something monitor
    
  • if the shutdown hangs or fails, one can use the stop script, which finds the pid and kills the process:
    Code Block
    
    $ ./stop
    
  • to check the status of the pipeline server, one you can use the ping function of the pipeline:
    Code Block
    glast@noric09 $ ./pipeline ping
    Pinged server version 1.3.5 running on glastlnx12.slac.stanford.edu since 2010-09-07 16:57:28.012