MAXRUN for cronjobs reached

[John Dominic T. Binuya]

Has anyone experienced this message:
! MAXRUN (100) procs reached Mon Sep 3 01:45:00 EAT 2007

all my cronjobs just stopped running. Any help would be greatly appreciated.

Thanks

[whiteknight]

Hi John,

Is this HPUX or Tru64 unix ?
Please paste

Check cron queuedefs:
# cat /usr/lib/cron/queuedefs (same file as /var/adm/cron/queuedefs)


WK
please assign points

[AwadheshPandey]

It looks like MAXRUN is hardcoded to 100. Changes in queuedefs (man queuedefs)will not increase the limit. The limit is for concurrent jobs. Is it possible that some of your jobs are running longer which is causing the limit to be met?

A possible workaround is to group your scripts in a larger script, then run the script from cron. Is that possible in your environment?

Also, if you are not time critical, perhaps increasing nwait in the queuedefs file will allow more jobs to complete.

[John Dominic T. Binuya]

I'm using HPUX

cat /usr/lib/cron/queuedefs
a.4j1n
b.2j2n90w
c.500j1n

What do you mean by assigning points?

Thanks so much for the help

[whiteknight]

Hi John,

Have you installed any cron patches, There is a known issue on this

PHCO_36533 11.23 at(1)/cron(1M)/crontab(1) cumulative patch
or
PHCO_35331 11.11 at/cron/batch cumulative patch

( CR:JAGaf54881 )
cron(1m) daemon can have maximum of only 100 jobs running.

WK
Please assign points

See the meaning of assign points
http://forums1.itrc.hp.com/service/forums/helptips.do?#33

[John Dominic T. Binuya]

Thank you very much for the quick replies. With regards to grouping the individual scripts, I am already asking our dev group to check the feasibility.

thank you again