Good morning

Since we had this week the "Typer Mismatch" problem due
to an auto-convert, we installed the latest release
of the 24x7 scheduler.

We modified the script to prevent the above mentioned
problem and installed, as was recommanded the v3.4.22 version.

The last two days at 22h00 the auto-restart option doesn't work
any more. Due to new release ?

Every night since several months already the scheduler, running
7/7 and 24/24 hangs around 21h55 every day the program; never
knew why, but found out that with an automatic restart at 22h00
the scheduler would ran again for nearly 24 hours.

Two questions :
- Why restart doesn't work anymore
- Why 24x7 still hangs around 22h00 (how to find out why)

Thanks again for helping
Robbert de GROOT

Please check what it is says in the job log. There should be some lines like "Attempting to restart...", "X jobs are still running restarting now may lead to unpredictable results."

The reason it hung is that it stops the scheduling engine and then attempts to kill active jobs. If it cannot it then infinitely waits for these jobs to finish which usually leads to the hanging. Because the scheduling engine is off, new jobs don't start. To avoid this problem set your jobs to run detached then the scheduler can easily kill them at any time.

: Good morning

: Since we had this week the "Typer Mismatch" problem due
: to an auto-convert, we installed the latest release
: of the 24x7 scheduler.

: We modified the script to prevent the above mentioned
: problem and installed, as was recommanded the v3.4.22 version.

: The last two days at 22h00 the auto-restart option doesn't work
: any more. Due to new release ?

: Every night since several months already the scheduler, running
: 7/7 and 24/24 hangs around 21h55 every day the program; never
: knew why, but found out that with an automatic restart at 22h00
: the scheduler would ran again for nearly 24 hours.

: Two questions : - Why restart doesn't work anymore
: - Why 24x7 still hangs around 22h00 (how to find out why)

: Thanks again for helping
: Robbert de GROOT

Ok, thanks for that. I'll put that in placeand
will wait untill tonight if the job restarts when "stopping".
If any problem I'll be back to you about that .
Thanks dor helping me out (again) ;-)

: Please check what it is says in the job log. There should be some lines like
: "Attempting to restart...", "X jobs are still running
: restarting now may lead to unpredictable results."

: The reason it hung is that it stops the scheduling engine and then attempts
: to kill active jobs. If it cannot it then infinitely waits for these jobs
: to finish which usually leads to the hanging. Because the scheduling
: engine is off, new jobs don't start. To avoid this problem set your jobs
: to run detached then the scheduler can easily kill them at any time.

The job stopped again, although the detatched option.
Is it also normal when running the job we get a popup
windows with asking running the jow in test mode or
normal mode.

Not being able to restart the job is a ereal handicap as this
request human intervention every day at 22h00

How can I figure out why the job stops. No information
in logging or what ever.

: Ok, thanks for that. I'll put that in placeand
: will wait untill tonight if the job restarts when "stopping".
: If any problem I'll be back to you about that .
: Thanks dor helping me out (again) ;-)

The popup appears only when you click the Run Now button and this is normal. If you select Test Mode the job will run in the foreground and all error messages (if any) will be displayed on the screen prompting you to select abort or continue options. If you run it in Normal mode the job runs in the background normally, no interactive message boxes are displayed and you can continue working with the GUI.

What do you mean by the "job stopped?" Did it crashed or completed with an error. Can you provide more details on this job? Were you able to restart the scheduler at 22:00?

PS. In case if you are talking about a script type job aborting abnormally enable tracing option in the Tools/Options/Log menu and after the job stops check the .log file in the Performance Data subdirectory. It will show every executed line and this way you can see where it stops.

: The job stopped again, although the detatched option.
: Is it also normal when running the job we get a popup
: windows with asking running the jow in test mode or
: normal mode.

: Not being able to restart the job is a ereal handicap as this
: request human intervention every day at 22h00

: How can I figure out why the job stops. No information
: in logging or what ever.

Tonight the 24x7 scheduler mixed up again. I'll put Monday
the logging on and will watch around 22h00. Keep you informed
Thanks

: The popup appears only when you click the Run Now button and this is normal.
: If you select Test Mode the job will run in the foreground and all error
: messages (if any) will be displayed on the screen prompting you to select
: abort or continue options. If you run it in Normal mode the job runs in
: the background normally, no interactive message boxes are displayed and
: you can continue working with the GUI.

: What do you mean by the "job stopped?" Did it crashed or completed
: with an error. Can you provide more details on this job? Were you able to
: restart the scheduler at 22:00?

: PS. In case if you are talking about a script type job aborting abnormally
: enable tracing option in the Tools/Options/Log menu and after the job
: stops check the .log file in the Performance Data subdirectory. It will
: show every executed line and this way you can see where it stops.

How did it go last night?

: Tonight the 24x7 scheduler mixed up again. I'll put Monday
: the logging on and will watch around 22h00. Keep you informed
: Thanks

gOOD MORNING

Since the last few days, the scheduler stops around 21h30 and 22h00
(no particulier events in Windows Journal) and no automatic restart
is done. No message showing up any problems.

What can be sent to you to make auto restart work again (like
it did before updating the 24x7 to v3.4.22

Robbert

: How did it go last night?

If you want you can roll back to version 3.4.21 while are working on this issue. Do you need a download link?

Another workaround for this issue is suggested here http://www.softtreetech.com/cgi_bin/config.cgi?read=3872
Don't forget to disable auto-restart options.

: gOOD MORNING

: Since the last few days, the scheduler stops around 21h30 and 22h00
: (no particulier events in Windows Journal) and no automatic restart
: is done. No message showing up any problems.

: What can be sent to you to make auto restart work again (like
: it did before updating the 24x7 to v3.4.22

: Robbert

The fact is that are two problems : The first one is that the scheduler stops
running the (only) job is runs the whole day. Why always near 22h00 ??

I found the workaround of auto-restart and everything was running ok (except of course
between the moment that the scheduler stops running and the 22h00 auto-restart time)

Comes the second question : why does Auto Restart not work anymore.

Of course I would like not the run other jobs to solve problems of main jobs. You understand that.

If we could find out why the scheduler stops running ...

Is teher anything I've or can sent you ?

: If you want you can roll back to version 3.4.21 while are working on this
: issue. Do you need a download link?

: Another workaround for this issue is suggested here
: http://www.softtreetech.com/cgi_bin/config.cgi?read=3872
: Don't forget to disable auto-restart options.

Because it always stops at the same time that means either it attempts to run or kill some job at that time or some other process is affecting the scheduler from outside (backup, anti-virus scanning in the job queue directory, ???)

First I would find jobs scheduled to run before 22h00 (or event-based jobs that are happen to run at that time). If necessary, enable logging and tracing options for all jobs which will allow you to see clearly what has happened before it stops.
Secondary, I would ensure that the main job is setup to run detached and in a separate job queue. This way it cannot affect the scheduler and no matter what happens to other jobs they cannot directly affect the main job.

: The fact is that are two problems : The first one is that the scheduler stops
: running the (only) job is runs the whole day. Why always near 22h00 ??

: I found the workaround of auto-restart and everything was running ok (except
: of course
: between the moment that the scheduler stops running and the 22h00
: auto-restart time)

: Comes the second question : why does Auto Restart not work anymore.

: Of course I would like not the run other jobs to solve problems of main jobs.
: You understand that.

: If we could find out why the scheduler stops running ...

: Is teher anything I've or can sent you ?

Thanks for all those ideas. We're especially tracing actually the backup processus
of the local 24x7 machine. There seem to be something strange that may be the orgine of
the problem.
I keep you informed.
Thanks for helping
Robbert

: Because it always stops at the same time that means either it attempts to run
: or kill some job at that time or some other process is affecting the
: scheduler from outside (backup, anti-virus scanning in the job queue
: directory, ???)

: First I would find jobs scheduled to run before 22h00 (or event-based jobs
: that are happen to run at that time). If necessary, enable logging and
: tracing options for all jobs which will allow you to see clearly what has
: happened before it stops.
: Secondary, I would ensure that the main job is setup to run detached and in a
: separate job queue. This way it cannot affect the scheduler and no matter
: what happens to other jobs they cannot directly affect the main job.

ALthough the problem of blocking our script (only, one is running)
the auto-restrt doesn't anyway. Could this be due to the problem
that stops the script ? Although an error message via email has been scheduled in case
of problems with the script, no message is send. Does
thescheduler she the "stopping" as a problem ?

I keep you informed
Robbert

: Because it always stops at the same time that means either it attempts to run
: or kill some job at that time or some other process is affecting the
: scheduler from outside (backup, anti-virus scanning in the job queue
: directory, ???)

: First I would find jobs scheduled to run before 22h00 (or event-based jobs
: that are happen to run at that time). If necessary, enable logging and
: tracing options for all jobs which will allow you to see clearly what has
: happened before it stops.
: Secondary, I would ensure that the main job is setup to run detached and in a
: separate job queue. This way it cannot affect the scheduler and no matter
: what happens to other jobs they cannot directly affect the main job.

Auto-restart can surely block the script if the timing is the same.
Why do you want to do the auti-restart anyway?
I am sure if you run that job with detached option you would not need to do that.

: ALthough the problem of blocking our script (only, one is running)
: the auto-restrt doesn't anyway. Could this be due to the problem
: that stops the script ? Although an error message via email has been
: scheduled in case
: of problems with the script, no message is send. Does
: thescheduler she the "stopping" as a problem ?

: I keep you informed
: Robbert