Several suggestions:
1. If possible, change jobs to run synchronous, if not all, than just some of them.
2. Verify that batch jobs don't spawn child processes, which never terminate.
3. Use the Windows 2000 Performance Monitor application to monitor handles and threads in 24x7.exe. If number of threads constantly increases with some job runs, please try to figure out the pattern and find out which job(s) is(are) causing that.
4. If the scheduler hangs again, please check how much free system resources are left and if not much you will need to find jobs that cause the memory leak.
5. Feel free to use this web board to report and discuss your 24x7 problems. : We have been using 24X7 Scheduler for about a year. Lately we have been
: plagued with problems where 24X7 hangs up and no other jobs are submitted.
: It is installed on a single workstation and has about 16 jobs on the
: schedule. The jobs are all fairly simple and most just submit RUNANDWAIT
: commands to execute DOS batch files which copy and move data around the
: network. Each batch file creates a log file during execution. After the
: batch file finishes, the contents of the log file is checked and an E-mail
: is sent specifying whether the job was successfull or not. When we had
: only 4 or 5 jobs the process was fairly stable. As more jobs were added,
: more hang-ups occurred. We originally were running under Windows95 but as
: the frequency of problems increased we moved to Windows 2000 Professional
: hoping the more stable operating system would help. We have kept current
: with new releases and are currently at v2.4.14. We are still hanging-up
: about once a week which is certainly not acceptable. Any suggestions or
: ideas?
|
