Macro Schedular Hanging

Larry Geisz · Post by **Larry Geisz** » Fri Jul 16, 2004 2:04 pm

Good Morning All,

I am currently using MS 7.2.043 to run monitoring task for my systems but the scheduler seem to be hanging a lot. I have put a process monitor on the MS and what it appears to be doing is using all of the processor and not releasing it. When this happens MS stops performing.

Has anyone else seen this?

Does anyone have a solution to this?

Macros Scheduler is at the heart of a lot of my monitoring for the company I work for and I would like to continue to use it.

Thanks

Larry Geisz

[email protected]

Bob Hansen · Post by **Bob Hansen** » Fri Jul 16, 2004 4:37 pm

Can you show the script? What is being monitored?

How is it loaded?

Runs continuously or on a schedule? If schedule, what frequency?

Any clues from looking at logfile for Macro Scheduler?

lgeisz · Post by **lgeisz** » Fri Jul 16, 2004 6:23 pm

The script just invokes a .cmd file. This script runs M-F 5 am till 11:55pm. This also happens on another machine I am using MS on it runs then hangs.

Currently on my monitoring machine this is the only script. On the other machine it is running a mixture of continuous and stopping and starting.

run>C:\PROV_MEM_EL.cmd

I have placed a monitor on MS using Segue's SilkVision thats how I know that it is using all of the processor when it hangs and also when it is hanging.

Lumumba · Post by **Lumumba** » Fri Jul 16, 2004 6:51 pm

I have a MSched (MS in some cases is confusing me as it's "owned" by MicroSoft

) script which has to run 24/7.

For whatever reason it hangs as well and I gave up after ages of time spent to identify what's going on. I had the (same?) idea if its blocking the memory/cpu as the MS! TaskManager showed an increasing memory block used by MSched. So I've implemented a scheduled restart (after a preset no. of loops - shutdown the app, restart the box, autologin with "a little help of a friend" named TweakUI) to reset the system at all.

Bob Hansen · Post by **Bob Hansen** » Sat Jul 17, 2004 3:15 am

You cannot have included all of the relevant script. There must be some type of a loop or some IF conditions that you are checking.

When you say this "runs" M-F, from 5 to 11:55, then I am still confused about what triggers it. Are you calling the script every minute? Every hour? When some file exists in some folder? When some window opens? What does the script do after running C:\PROV_MEM_EL.cmd ?

1. Assume script starts on Monday at 5am.
2. It runs "C:\PROV_MEM_EL.cmd "
3. It does nothing else. Macro Scheduler is done if that is the whole script.

Have you tried using Let>RP_WAIT=1 before running PROV_MEM_EL.cmd ?
It is possible that PROV_MEM_EL.cmd is actually causing your problem?

Guest · Post by **Guest** » Mon Jul 19, 2004 1:48 pm

The script only kicks off the .cmd prompt. Nothing else the script I posted is the complete script. I did forget to say that the script runs every 10 minutes between the listed hours. After the script runs it waits to run again. I have not tried any of your suggestions ( I would not think I would have to for the system hanging). The problem in my opinion is not with the script but with Macro Scheduler.

lgeisz · Post by **lgeisz** » Mon Jul 19, 2004 1:57 pm

The last Guest reply was from me I forgot to log in

Larry Geisz

Bob Hansen · Post by **Bob Hansen** » Mon Jul 19, 2004 3:07 pm

OK, have better understanding of how script triggers.

What do you mean when you say

but the scheduler seem to be hanging a lot..... When this happens MS stops performing

What are the symptoms? The only symptom that I can see is that either it does not start at the scheduled time, or it does not call your program.

The Macro Scheduler is always running in the background, but the Macro script will be done instantly.

Again the steps that should be happening are:
1. Time to fire Macro Scheduler
2. Macro Scheduler starts your program.
3. Macro Scheduler is done, closes.
4. 10 minutes pass by and start again at step 1.

What does your log file show?
Is Macro Scheduler starting every 10 minutes.
Is Macro Scheduler calling the program?
Does log show that Macro Scheduler completed macro?

You should see log contents that looks something like this:

7/16/2003 05:10:00:000 - Started Macro : ProvMem
7/16/2003 05:10:00:000 - run>C:\PROV_MEM_EL.cmd
7/16/2003 05:10:00:000 - Finished Macro : ProvMem
7/16/2003 05:20:00:000 - Started Macro : ProvMem
7/16/2003 05:20:00:000 - run>C:\PROV_MEM_EL.cmd
7/16/2003 05:20:00:000 - Finished Macro : ProvMem
7/16/2003 05:30:00:000 - Started Macro : ProvMem
7/16/2003 05:30:00:000 - run>C:\PROV_MEM_EL.cmd
7/16/2003 05:30:00:000 - Finished Macro : ProvMem
7/16/2003 05:40:00:000 - Started Macro : ProvMem
7/16/2003 05:40:00:000 - run>C:\PROV_MEM_EL.cmd
7/16/2003 05:40:00:000 - Finished Macro : ProvMem

How does the log file change if you add Let>RP_WAIT ahead of the run command? What if C:\PROV_MEM_EL program is not done/closed in the next 10 minutes, do you still want to load another copy?

What does C:\PROV_MEM_EL program do?
How does C:\PROV_MEM_EL program end?
The process you describe will load 6 copies into memory every hour, or 114 copies every day according to your schedule. Maybe using up some resources?

Suppose you replace " run>C:\PROV_MEM_EL.cmd " with another program to help diagnose this problem. This would help to see if Macro Scheduler is the problem or if C:\PROV_MEM_EL program is the problem.

You can also modify the script to loop every 10 minutes between 5am and midnight. vs. having the scheduler call it every 10 minutes. Again, use Let>RP_WAIT=1 in the loop to prevent loading multiple copies of C:\PROV_MEM_EL program. Again, make a log and look at results.

lgeisz · Post by **lgeisz** » Mon Jul 19, 2004 3:34 pm

I have not checked the logs yet. The symptom seems to be that sometime during a run MS will use all of the CPU resources (100% cpu utilization) and hang in that state. When this happens MS will not respond I have to close the program by using the Ctrl+Alt+Delete function.

The .cmd calls another program that runs a monitoring program.

Every time that I have had MS hang while I was monitoring it, it always shows the same CPU state I am monitoring 2 different machines running MS and it happens to them both.

I understand the thought behind the idea that the process may still be running when MS tryÃ¢â‚¬â„¢s to run again but the program that the .cmd file calls only runs for between 3 and 4 minutes and if it fails I get a notification.

Although looping the script is a good idea it is not feasible with third parties that we are monitoring for want to be able to adjust the monitoring time (they would not have a clue how to script this and I am often off to the next project and have limited time).

Again my big concern is to find out why MS is grabbing all of the CPU and then freezing or hanging up.

lgeisz · Post by **lgeisz** » Mon Jul 19, 2004 3:39 pm

Just to update the logging issue it was not turned on for this script.

Bob Hansen · Post by **Bob Hansen** » Mon Jul 19, 2004 4:47 pm

I think that I have exhausted all of my suggestions for you to try.

I am sure that others will have some other ideas for you to consider also.

Good luck,

lgeisz · Post by **lgeisz** » Mon Jul 19, 2004 4:55 pm

Thanks Bob