"queue max run limit reached" in /var/adm/cron/log

[Vincent Lam_1]

The cronjob sudden failed to run and we keep seeing the following error in /var/adm/cron/log.

Any clue?

! c queue max run limit reached Fri Nov 12 19:40:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:40:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:40:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:40:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:41:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:41:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:41:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:41:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:42:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:42:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:42:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:42:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:43:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:43:00 EAT 2004 ! c queue max run limit reached Fri Nov 12 19:43:00 EAT 2004 ! rescheduling a cron job Fri Nov 12 19:43:00 EAT 2004

[Robert-Jan Goossens]

Hi Vincent,

Check this doc.

Document description: How to resolve a queue max run limit reached
Document id: HPUXKBRC00000644

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063199330

Regards,
Robert-Jan

[Sridhar Bhaskarla · Accepted solution]

Hi,

Look at your /var/adm/cron/queuedefs file. It's the configuration file that specifies how many cronjobs can be handled by cron simultaneously. It's usually in this format.

c.xjyn

This meanx 'x' number of cronjobs can run simultaneously.

If you have more than 10 jobs running at the same time (look at all the crontab files under /var/spool/cron/crontabs directory), I suggest you change the timings. Or you can modify the queuedefs above and change the value x to a higher number and restart cron (using /sbin/init.d/cron script)

-Sri

[Sridhar Bhaskarla]

Hi Vincent (again),

I should have added. If you started to see this problem all of a sudden without any change in the crontab configuration by the users, then look at all the running processes and see if there are any jobs that started through cron earlier but are hanging now. Note the pid of 'cron' (unless you have restarted it recently) and see if there are any processes whose parent pid is that of cron. Kill those processes that are hung.

-Sri

[Vincent Lam_1]

Thanks all for the help. It turned out that a user has written a cronjob which "never exits". The issue is now solved. Thanks all for the help.

Vincent

[guldasta]

Hi Sridhar, I have the same problem. I have changed queue number from 100 to 200, but still encountering the same problem. queue max run limit reached in cron log. It runs for couple of days and only then displays this error. What can I do to resolve this? When I comment out this particular job, I dont encounter a problem. but when I do rub this job it keeps maxinbg out on queue. Please help!