How to shutdown and restart the pipeline server

Created by Maria Elena Monzani, last modified on Sep 08, 2010

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

To stop and start the pipeline automatically (for a planned outage):

first of all, login as glast to some interactive machine and go to the pipeline directory:
```
$ ssh glast@noric
$ cd ~glast/pipeline-II/prod/
```

create and edit a shutdown_schedule_date file:

$ date > shutdown_schedule_20100909
$ vim shutdown_schedule_20100909

the shutdown_schedule_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:
```
Thu Sep  9 09:50:00 PDT 2010
Thu Sep  9 13:50:00 PDT 2010
```

create a symbolic link for shutdown_schedule_date as shutdown_schedule:
```
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)

to restart the pipeline, just remove the symbolic link (leaving the shutdown_schedule_date file for future reference):
```
rm shutdown_schedule
```

the pipeline should go back up automagically in a few minutes

to check the status of the pipeline server, one can use the ping function of the pipeline:

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:
```
$ 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):
```
$ mv monitor monitor_something_something
```

shutdown the pipeline server with the shutdown command:
```
$ ./pipeline shutdown
```

restart the pipeline using the start script:
```
$ ./start
```

move back the monitor script to its original location:
```
$ mv monitor_something_something monitor
```

if the shutdown command hangs or fails, one can use the stop script, which finds the pid and kills the process:
```
$ ./stop
```

to check the status of the pipeline server, one can use the ping function of the pipeline:

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

No labels