My box that runs 24x7 has been running for 35 days,
in this time 24x7 has been running continuously and
executing jobs every 2 minutes. Recently the machine
started performing very badly - jobs started queuing up
and some were skipped because they where to late.

I closed 24x7 and re-opened it and everything was fine
again without even having to reboot the machine.

None of the scripts are leaking any resources and the
machine has loads of memory.

Any ideas?

Were there any hanged jobs or jobs that ran much longer than usual and that caused other jobs to be late?

Could it be that your jobs directly or indirectly create temporary file and the do not delete them?
Do you get significant system swap file fragmentation or other cumulative impacts after a while?

How do you know your jobs do not cause resource leaking?

: My box that runs 24x7 has been running for 35 days,
: in this time 24x7 has been running continuously and
: executing jobs every 2 minutes. Recently the machine
: started performing very badly - jobs started queuing up
: and some were skipped because they where to late.

: I closed 24x7 and re-opened it and everything was fine
: again without even having to reboot the machine.

: None of the scripts are leaking any resources and the
: machine has loads of memory.

: Any ideas?

Yes, my jobs run with a 2 min interval. There were ones that missed their
time slot. The jobs log their actions in various logs files, I checked and
very file that is very opened is closed.

Overall the entire machine was slugish. After closing and opening 24x7
everyting was back to normal.

Would it perhaps help to run all the jobs detached?

Cheers :)
: Were there any hanged jobs or jobs that ran much longer than usual and that
: caused other jobs to be late?

: Could it be that your jobs directly or indirectly create temporary file and
: the do not delete them?
: Do you get significant system swap file fragmentation or other cumulative
: impacts after a while?

: How do you know your jobs do not cause resource leaking?

You can try that, but if you don't have memory leaking or stability problems this is not needed.

You need to monitor you computer and find out which performance statistics consistently growth over the time. Also monitor number of files in the temp directory and swap file size/fragmentation. Please let us know what you find so we can suggest how to deal with this problem.

: Yes, my jobs run with a 2 min interval. There were ones that missed their
: time slot. The jobs log their actions in various logs files, I checked and
: very file that is very opened is closed.

: Overall the entire machine was slugish. After closing and opening 24x7
: everyting was back to normal.

: Would it perhaps help to run all the jobs detached?

: Cheers :)