First you need to find out which job(s) was running at that time and if that possible caused the scheduler to exit. Especially if you have a job that kills a process using ProcessKill or closes a window by sending keystrokes or using WindowClose (in other words that you don't shoot yourself in a foot). In case if that happens again, before you restart the scheduler, check what you have in the job queue directories, that will help you to determine pending and running jobs. Also start the Win2000 Performance Monitor and setup it to monitor 24x7.EXE process (virtual memory, number of threads and number of open handles). That can help you to determine if there are jobs that cause resource leaking. Pay special attention to database jobs if you have any. Database middleware can often be a cause or resource leaking and eventually bring the client application down. If you find "troublemaking" jobs set them to run "detached" using the detached property so they in their own memory space and cannot affect the system. If you run 24x7 in the Master mode, turn on tracing option and next time the system shuts down, check the master.log file for errors. You can create a job in 24x7 to monitor the main 24x7 executable module. That job can be started on the Windows startup from the "Start Up" folder using 24x7 /JOB shortcut. The job should have "no schedule" type and use simple script with a ProcessList statement to count how many instances of 24X7.EXE you have. If it will find just 1 instance, it would mean the main instance is down. You can program the job logic to restart the main instance and send you some notification email or do something else what you consider as an appropriate action. : Greetings: We're running 24X7 v3.2.2 on a Windows2000 Professional PC with a
: Pentium II - 233Mhz processor and 384MB RAM. The 24X7 is running on the
: desktop, not as a service. About every other day the scheduler will
: shutdown (disappear from the desktop) at the same time (according to the
: entries in the log). There are no entries that suggest what's going on in
: the Windows Event Viewer. There are no errors in the scheduler log that
: suggest a problem. This is the only application runing on this PC. The
: jobs that is is kicking off around that time are jobs that it has kicked
: off multiple times earlier in the day with no problems. Any ideas or
: suggestions? : On a similar note, I would like to setup a job either with AT commands or the
: Windows Task Scheduler that could run every 5 or 10 minutes to check if
: 24X7 is running. If it is running, exit. If it's not running, start it. It
: would be a simple thing inUNIX, but..... Does anyone have a suggestion on
: how to do this in Windows2000? : Thanks! : Neil.....
|
