CronJobs Failing in IBM-AIX

If cron jobs are failing and reports are not getting generated.

Follow the below steps to fix it.

Go to /var/adm/cron

cat log or tail -f log

Check the Log file and find the issue why jobs are getting failed. If the error code is

#Error — 0481–087 The c queue maximum run limit has been reached.

If you are getting this error, it means your queue limit is reached.

Now check the queuedefs file at the bottom something like this should be there

b.50j20n60w

which
is basically your number of jobs and other things.

So check if the number of jobs mentioned is 50

vi this file queuedefs
vi queuedefs (Increase the value of jobs from 50 to 200 something like this.)

c.200j2n60w.

So now it will take 200 jobs parallelly & no need to kill existing cron job.

You can just change the value (Increase from lower to Higher) it will automatically respawn again.

# b.50j20n60w
c.200j2n60w

If your queue limit is reached than we can check in the logs

cron: 0481–087 The c queue maximum run limit has been reached.
Fri Jan 5 17:34:00 EST 2018

we will get this error

so simply increase the jobs limit under /var/adm/cron/ quedefs
from 50 to 200


c.200j2n60w
here
C = maximum number of cron events
200j= maximum number of jobs in this queue
2n = nice value at which these jobs will run at default is 2
60w= wait time till next execution attempt (default is 60 seconds)

earlier it was b.50j20n60w
b stand for batch jobs


c.200j2n60w
this would set the cron queue to a maximum of 200 jobs, with a nice value of 2, and a wait time of 60 seconds.


“Lower the nice value, higher will be the priority of the job”.