cron log - c queue max run limit

jasper_2 — Tue, 19 Mar 2002 05:00:58 GMT

Hi,

we encountered this on our md server...cron is running if you do ps -ef|grep cron but actualy the daemon doesnt do anything...

found the message below at /var/adm/cron/log file.

! c queue max run limit reached Tue Mar 19 08:00:00 EAT 2002
! rescheduling a cron job Tue Mar 19 08:00:00 EAT 2002

do i need to adjust anything to resolve this?

thanks.

Re: cron log - c queue max run limit

Michael Tully — Tue, 19 Mar 2002 05:05:02 GMT

Hi,

This is a document from the Technical Knowledge Base. It should solve your problem.

Michael

How to resolve a queue max run limit reached DocId: HPUXKBRC00000644 Updated: 7/20/01 6:55:00 AM

PROBLEM
All atjobs are not executing when scheduled. The /var/adm/cron/log file shows the following entry:
! a queue max run limit reached Wed Jan 12 09:59:20 PST 2000
! rescheduling at job Wed Jan 12 09:59:20 PST 2000

RESOLUTION
Use the following commands to check for version of cron and at. Make sure that the versions are current.

The versions can be updated by installing the latest cumulative cron patch.

# what /usr/bin/cron

# what /usr/bin/at

# crontab -l

# cat /usr/lib/cron/queuedefs

# swlist -l fileset |grep cron

Check the queuedefs file to see how many atjobs are currently configured to run simultaneously per queue.

NOTE: The total number of jobs running in all queues is 40.

The output will look as follows:

q.[njobj][nicen][nwaitw] the queues is limited to 40.

nice - The nice value to give to all jobs in that queue that not run with a user ID of super-user (see nice(1)). The default value is 2.

Where:

q - The name of the queue, such that a is the default queue for jobs started by at (see at(1)), b is the queue for jobs started by batch (see batch(1)), and c is the queue for jobs run from a crontab file (see crontab(1)). Queue names d through y designate user-defined queues.
njob - The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, the total number of jobs that can be run on all

nwait - The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because more than 40 jobs were running in all the queues (see njob above).

EXAMPLE:

# cat /usr/lib/cron/queuedefs

a.4j1n
b.2j2n90w
c.100j1n
NOTE: The a queue, by default, can run 4 jobs simultaneously.

NOTE: The c.100j1n means 100 cron/at/batch jobs can be run similatenously with a nice value of 1.

To increase that number, modify the queuedefs file and restart cron.

The follow example increases the limit from 4 to 10 simultaneous jobs.

Modify the queuedefs file:

# vi /var/adm/cron/queuedefs

a.4j1n --> change this to the following line
a.10j1n

Stop Cron:

# ps -ef |grep cron

# kill {cron_pid}

NOTE: This defaults to a -15 which kills nicely.

Restart cron:

# /sbin/init.d/cron

Re: cron log - c queue max run limit

Patrick Wallek — Tue, 19 Mar 2002 05:08:39 GMT

Have a look at TKB document KBRC00000882. The document is attached for your convenience.

Note that this document is for HP-UX 10.20.

topic Re: cron log - c queue max run limit in Operating System - HP-UX

cron log - c queue max run limit

Re: cron log - c queue max run limit

Re: cron log - c queue max run limit