Hi,

We use 24x7 as a service and this works just fine.
Only once a week on sunday the server is rebooted using the sheduled tasks.
After the reboot all jobs stop running and the following message always comes
up in the log : Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!.

If we stop and start the 24x7 service everything works just fine again.

Any ideas?

This indicates that job #3 is being detached and that job is being run during shutdown. At the time of the shutdown 24x7 terminates the job. That's all.

: Hi,

: We use 24x7 as a service and this works just fine.
: Only once a week on sunday the server is rebooted using the sheduled tasks.
: After the reboot all jobs stop running and the following message always comes
: up in the log : Forced shutdown. Process '24x7.exe /JOB 3' has been
: terminated!.

: If we stop and start the 24x7 service everything works just fine again.

: Any ideas?

: This indicates that job #3 is being detached and that job is being run during
: shutdown. At the time of the shutdown 24x7 terminates the job. That's all.

The problem is that all jobs after the shutdown have this message in the log and
don't run.
The sheduler only starts working normally again after we stop and re-start the 24x7 service.

The message simply indicates that the scheduler senses the shutdown and terminates running jobs. Whether it completes the process or it gets killed by the system before that I don't know.
Please check what you have in system options. Make sure "reset job queues on startup" option is set. If it isn't, enable it so that the scheduler can start fresh after the restart.

: The problem is that all jobs after the shutdown have this message in the log
: and
: don't run.
: The sheduler only starts working normally again after we stop and re-start
: the 24x7 service.

Please post a portion of the schedule.log file demonstrating the issue including messages around "shutdown detected", "scheduler terminating" and "scheduler starting"

: This option was already enabled.
: Anything else we can check?

: Please post a portion of the schedule.log file demonstrating the issue
: including messages around "shutdown detected", "scheduler
: terminating" and "scheduler starting"

This is what can be found in the log file :

2/07/2006 12:00:01 0 3 0 Order Upload between 08:00 and 14:20 every 10 min Job finished.
2/07/2006 12:08:29 0 0 0 24x7 Scheduler [24x7 service] 24x7 Scheduler starting...
2/07/2006 12:10:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 12:20:01 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 12:30:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 12:40:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 12:50:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 13:00:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 13:10:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
2/07/2006 13:20:01 1 3 0 Order Upload between 08:00 and 14:20 every 10 min Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!

This job runs from 08:00 till 17:00 every 10 minutes and a reboot of the server is scheduled at 12:05 on Sunday.

I think you have a job #3 set to run detached and synchronous and in job properties you have set the scheduler to kill this job if it runs for longer then 10 minutes. What you see in the job log is simply a warning written by the scheduler that it is killing the job.

: This is what can be found in the log file : 2/07/2006 12:00:01 0 3 0 Order
: Upload between 08:00 and 14:20 every 10 min Job finished.
: 2/07/2006 12:08:29 0 0 0 24x7 Scheduler [24x7 service] 24x7 Scheduler
: starting...
: 2/07/2006 12:10:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 12:20:01 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 12:30:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 12:40:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 12:50:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 13:00:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 13:10:00 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!
: 2/07/2006 13:20:01 1 3 0 Order Upload between 08:00 and 14:20 every 10 min
: Forced shutdown. Process '24x7.exe /JOB 3' has been terminated!

: This job runs from 08:00 till 17:00 every 10 minutes and a reboot of the
: server is scheduled at 12:05 on Sunday.

: The message simply indicates that the scheduler senses the shutdown and
: terminates running jobs. Whether it completes the process or it gets
: killed by the system before that I don't know.
: Please check what you have in system options. Make sure "reset job
: queues on startup" option is set. If it isn't, enable it so that the
: scheduler can start fresh after the restart.
That's right but in this case the job get's killed even before doing any processing (not 10 min).
After re-starting the 24x7 service, everyhing works fine again.

I am not sure what else can be done here. You can try setting the job to launch from a script, in JAL it will look like

Dim pid, number
Run "your command line here", "", pid

In this scenario the scheduler will start the job but will not follow it and will not attempt to terminate it on shutdown.

: That's right but in this case the job get's killed even before doing any
: processing (not 10 min).
: After re-starting the 24x7 service, everyhing works fine again.