What a great solution to my problems, auto-restart the scheduler to clear out the job queues, too bad it does not work. I am running the scheduler on NT 4.0, and not as a service. I enabled periodic restarts. I then selected the time and day options. When the time comes to restart, the scheduler makes a entry in the log Restarting..., then the job clock freezes, and the scheduler never restarts. The scheduler is not locked up, but no other jobs run because the job clock is frozen at the restart time.

I guess it hangs while trying to terminate already running jobs.

If you know which processes should be cleared before restarting schedule a script type job using ProcessKill statement or schedule a program type job using ProcessKill command line utility that can be find in the 24x7 Tips and Scripts archive.

: What a great solution to my problems, auto-restart the scheduler to clear out
: the job queues, too bad it does not work. I am running the scheduler on NT
: 4.0, and not as a service. I enabled periodic restarts. I then selected
: the time and day options. When the time comes to restart, the scheduler
: makes a entry in the log Restarting..., then the job clock freezes, and
: the scheduler never restarts. The scheduler is not locked up, but no other
: jobs run because the job clock is frozen at the restart time.

There were no other processes running, all the job queues were empty, the server had just been restarted, the scheduler had just been restarted, there were only jobs scheduled to run in the future. I tried it several times, it hangs consistantly.

Ted.

: I guess it hangs while trying to terminate already running jobs.

: If you know which processes should be cleared before restarting schedule a
: script type job using ProcessKill statement or schedule a program type job
: using ProcessKill command line utility that can be find in the 24x7 Tips
: and Scripts archive.

Do you have 24x7 in the system path? Can you run it from anywhere using 24x7.exe command?
Which NT service packs you have installed on the system?

: There were no other processes running, all the job queues were empty, the
: server had just been restarted, the scheduler had just been restarted,
: there were only jobs scheduled to run in the future. I tried it several
: times, it hangs consistantly.

: Ted.

24x7 is in the system path, and yes it can be ran from the command line from anywere using 24x7.exe. The server is running NT 4.00.1381 (Service Pack 6).

: Do you have 24x7 in the system path? Can you run it from anywhere using
: 24x7.exe command?
: Which NT service packs you have installed on the system?

Please try this:

Create new JAL script type job. Copy the following code to the job script

Dim old_process_id, number
Dim new_process_id, number

ProcessGetID "24X7.EXE", old_process_id
Run "24X7.EXE", "", new_process_id
ProcessKill old_process_id

Schedule this job to run as needed. If it does not work please let me know on which line it fails.

: 24x7 is in the system path, and yes it can be ran from the command line from
: anywere using 24x7.exe. The server is running NT 4.00.1381 (Service Pack
: 6).

This script works perfectly. The only problem is that I get the notification that another instance of 24x7 Scheduler is already running on this computer.

Ted.

: Please try this: Create new JAL script type job. Copy the following code to
: the job script

: Dim old_process_id, number
: Dim new_process_id, number

: ProcessGetID "24X7.EXE", old_process_id
: Run "24X7.EXE", "", new_process_id
: ProcessKill old_process_id

: Schedule this job to run as needed. If it does not work please let me know on
: which line it fails.

: This script works perfectly. The only problem is that I get the notification
: that another instance of 24x7 Scheduler is already running on this
: computer, therefore it disables the job timer on the second instance.

: Ted.

My mistake, I only had the second instance problem during debugging, once it was schedule it works perfect. Thanks for the tip.

Ted.

: This script works perfectly. The only problem is that I get the notification
: that another instance of 24x7 Scheduler is already running on this
: computer.

: Ted.

Is anyone else experiencing this problem once again? We upgraded
from v3.4.13 to v3.4.18 last week & have been experiencing
problems with jobs not running.

After some investigation we've realized that all jobs
after a schedule auto-restart did not kick off. Here's what we
see when the auto-restart runs:

- Job clock stops
- "restarting...." added to the log
- Thread count of 24x7 decreases by 1
- CPU for 24x7 goes to 30-50% (dual system)
- 24x7 never restarts

I'd use the script in this thread, but it won't work
if we've got multiple async 24x7.exe's running.

Mike

: My mistake, I only had the second instance problem during debugging, once it
: was schedule it works perfect. Thanks for the tip.

: Ted.

What actually happens is 24x7 fails to kill all running jobs or jobs that hanged before restart. It hangs waiting for these jobs to terminate.

A 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.

: Is anyone else experiencing this problem once again? We upgraded
: from v3.4.13 to v3.4.18 last week & have been experiencing
: problems with jobs not running.

: After some investigation we've realized that all jobs
: after a schedule auto-restart did not kick off. Here's what we
: see when the auto-restart runs: - Job clock stops
: - "restarting...." added to the log
: - Thread count of 24x7 decreases by 1
: - CPU for 24x7 goes to 30-50% (dual system)
: - 24x7 never restarts

: I'd use the script in this thread, but it won't work
: if we've got multiple async 24x7.exe's running.

: Mike