| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Restart behaviour
If you restart the JobScheduler via JOC (Menu->'Terminate and restart') or with the startscript
| Code Block |
|---|
./bin/jobscheduler.sh restart
|
...
You can restart the JobScheduler with a timeout (in seconds) via JOC (Menu->'Terminate and restart within ~60s') or with the startscript
| Code Block |
|---|
./bin/jobscheduler.sh command "<terminate restart='yes' timeout='60'/>"
|
...
Note that the timeout for terminate in JOC is configurable in the ./config/operations_gui/custom.js (see also here).
See also http://www.sos-berlin.com/doc/en/scheduler.doc/termination.xml
JobScheduler remains in the status stopping
If you have an endless task then the JobScheduler remains endless in the status "stopping" after a normal restart without a timeout.
In this case you must abort and restart the JobScheduler via JOC (Menu->'Abort immediately and restart') or via the startscript
| Code Block |
|---|
./bin/jobscheduler.sh command "<modify_spooler cmd='abort_immediately_and_restart'/>"
|
...
Please avoid endless tasks!