Board index Solaris

"c queue max run limit reached" in cron logs, ???

"c queue max run limit reached" in cron logs, ???

Post by Cellinc » Sat, 27 Jul 2002 05:21:20



The cron process was still running, but the cron jobs have not been done at
all, and I got this message in /var/cron/log file 8 times every minute. Any
one who has any idea what's that?
After I restart cron, the problem is solved. But I want to know why. Thanks
!!
! c queue max run limit reached Mon Jul 15 02:18:00 2002
! rescheduling a cron job Mon Jul 15 02:18:00 2002
! c queue max run limit reached Mon Jul 15 02:18:00 2002
! rescheduling a cron job Mon Jul 15 02:18:00 2002
! c queue max run limit reached Mon Jul 15 02:18:00 2002
! rescheduling a cron job Mon Jul 15 02:18:00 2002
 
 
 
Top

"c queue max run limit reached" in cron logs, ???

Post by Chris Thomps » Sat, 27 Jul 2002 06:42:29




>The cron process was still running, but the cron jobs have not been done at
>all, and I got this message in /var/cron/log file 8 times every minute. Any
>one who has any idea what's that?
>After I restart cron, the problem is solved. But I want to know why. Thanks
>!!
>! c queue max run limit reached Mon Jul 15 02:18:00 2002
>! rescheduling a cron job Mon Jul 15 02:18:00 2002
>! c queue max run limit reached Mon Jul 15 02:18:00 2002
>! rescheduling a cron job Mon Jul 15 02:18:00 2002
>! c queue max run limit reached Mon Jul 15 02:18:00 2002
>! rescheduling a cron job Mon Jul 15 02:18:00 2002

Unless you have done something strange with /etc/cron.d/queuedefs, that
means that cron is already running as many jobs as it can handle, namely
100. Probably you have a crontab that kicks off jobs that never terminate.
You should be able to identify them from the /var/cron/log entries, or
alternatively by using "ptree [pid-of-cron]".

Chris Thompson
Email: cet1 [at] cam.ac.uk

 
 
 
Top

"c queue max run limit reached" in cron logs, ???

Post by Cellinc » Sat, 27 Jul 2002 23:14:07


The problem turned out to be a poorly-behaved job that didn't
exit (and was getting called several times an hour), thus
causing lots of children cron was awaiting. Corrected the job
script to exit properly, killed off the muiltitudinous jobs,
restart cron, things returned to normal.

Thanks!




> >The cron process was still running, but the cron jobs have not been done
at
> >all, and I got this message in /var/cron/log file 8 times every minute.
Any
> >one who has any idea what's that?
> >After I restart cron, the problem is solved. But I want to know why.
Thanks
> >!!
> >! c queue max run limit reached Mon Jul 15 02:18:00 2002
> >! rescheduling a cron job Mon Jul 15 02:18:00 2002
> >! c queue max run limit reached Mon Jul 15 02:18:00 2002
> >! rescheduling a cron job Mon Jul 15 02:18:00 2002
> >! c queue max run limit reached Mon Jul 15 02:18:00 2002
> >! rescheduling a cron job Mon Jul 15 02:18:00 2002

> Unless you have done something strange with /etc/cron.d/queuedefs, that
> means that cron is already running as many jobs as it can handle, namely
> 100. Probably you have a crontab that kicks off jobs that never terminate.
> You should be able to identify them from the /var/cron/log entries, or
> alternatively by using "ptree [pid-of-cron]".

> Chris Thompson
> Email: cet1 [at] cam.ac.uk

 
 
 
Top

1. Boot problem "VFS: file-max limit 8192 reached" anyone help?

Hi all.

I had a surprise booting up to Mandrake 7.2 today.

Boot was correct from hdb1, with all hardware and drivers loaded ok. No
hint of trouble until logon was complete. After Last Logon date, the
error in the subject header is given, then the kernel proceeds to
attempt to load the ld-linux.so.2 module.

It waits a while then returns the syntax "Unable to load interpreter
/lib/ld-linux.so.2".

If I attempt to "startx", I get the syntax "blah blah(path&filename):Too
many files open in system".

Looks like a memory or virutal ram problem. But I am not in the least
any sort of expert in such matters.

Unfortunately I can't remember if I was stuffing around with any
Mandrake x settings to cause this...

Anyway, I thought it might be a boot sector problem, because I recently
had to re-install (dare I say it...) Win 98 SE (on a completely separate
drive and partition, so I booted from kernel floppy, but got the same
problem. Don't remember seeing this before re-installing LILO after the
win install. But there again, I simply dont' recall, as I've been too
busy at work to logon at home for a long while... (any excuse).

Can anyone venture a guess as to the cause and (hopefully) solution to
my dilemma?

I appreciate your assistance,

Regards, Sean.

2. Compile error 2.4.1-pre8

3. inode overflow; c queue max run limit reached

4. StarOffice Printing...

5. cron: 0481-087 The c queue maximum run limit has been reached.

6. Cross over cable?

7. cron: b queue max run limit exceeded

8. Making a web server non-case sensitive

9. GETSERVBYNAME()????????????????????"""""""""""""

10. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

11. "Logging" or "Log structured" file systems with news spool.

12. FlexFax: Can not reach "fax" service at host "127.0.0.1"

13. Max Queue Limit Reached


All times are UTC
Board index