Recent log entries with multiple "Reached processing limit on queue processing: ..."

mark_anthony - May 19, 2009 - 12:58
Project:Notifications
Version:6.x-2.0
Component:Miscellaneous
Category:support request
Priority:critical
Assigned:Unassigned
Status:active
Description

My site has been running incredibly slow if at all sometimes, The Recent log entries page shows multiple entries of : "Reached processing limit on queue processing: ..."

In Details, the Type is listed as : notifications. Does this mean it is being generated from the Notifications module?

These entries are like a minute apart, if that much.

I have attached a screenshot of the dblog screen.

#1

mark_anthony - May 19, 2009 - 12:59
AttachmentSize
dblog_screenShot.jpg 209.85 KB

#2

gregarios - May 25, 2009 - 07:16

My site is not running slow, but my symptoms are similar:

  • Reached processing limit on queue processing (no matter how high it is set, I get this after less than a minute, even with the error message reporting an hour of time available- 3600)
  • No emails are sent out
  • No emails go through the queue dispite having it set to do so.

I have emails set to HTML by default.

I'm running:
FreeBSD 6.3, Apache 2.2.11, PHP 5.2.9, MySQL 5.0.75, Drupal 6.12, Notifications/Messaging 6.x-2.0, PHPMailer 5.02

#3

Jose Reyero - June 11, 2009 - 16:19
Status:active» postponed (maintainer needs more info)

This may happen if you either mess with the process limit options or if you don't run cron often enough.

So, settings? how many rows in queue? how often do you run cron?

Which specific processing limit is hit? (Full message).

#4

gregarios - June 12, 2009 - 05:20

I can have 2 short messages, and run cron every 15 minutes, and have virtually nothing else going on on the server. No matter the limits set in the Notifications settings, it still gives this "Reached processing limit" error. In fact, the processing limit can be set for thousands of seconds, and it'll still timeout in about 3 seconds after cron runs.

#5

cardentey - August 24, 2009 - 19:09

Hi:

I had the same problem and changed the following line in file notifications.cron.inc and solved the problem.

line 128:
$cronstart = time(); //variable_get('cron_semaphore', time());

variable "cron_semaphore" is Boolean. This is correct?

Thanks.

#6

Jose Reyero - September 22, 2009 - 12:10

Nope, cron semaphore is numeric (time).

You guys using poormanscron?

#7

Dave Kinchlea - September 25, 2009 - 16:02
Status:postponed (maintainer needs more info)» active

I'm using Elysia Cron running every minute with notifications running every 15 minutes and am having exactly the same problem ... the processing limit from the notifications admin page is meaningless on my site, it fails almost immediately after starting regardless of what large value I put there. This is not a case of too many records to review. The "fix" above did not fix my site but setting all notifications limits to 0 did... this will suffice for the time being but, of course, defeats the purpose of having those limits in the first place.

#8

jwarner - October 5, 2009 - 16:53

subscribing

#9

Jose Reyero - October 5, 2009 - 17:19

Important warning: Using % of cron time won't work.

Drupal 6.14 broke backwards compatibility for this, though that will be fixed in the next release. See http://drupal.org/node/193383

In the meanwhile, don't use % of cron time, use absolute time values instead.

#10

jwarner - October 5, 2009 - 18:29

I also see a list of "Reached processing limit on queue processing" messages in my recent log entries page. However, I am using the number of messages limit to *avoid* the manifestation of another problem - namely, my process dying and (what I consider to be much more serious) problem of duplicate messages being sent, which I talk about here: #574974: Multiple copies of the same message sent to the same user

Is this considered an appropriate use of the processing limit field?

#11

Dave Kinchlea - October 7, 2009 - 13:12

It's probably bad form replying to oneself, however....After much searching and having gone outside of Drupal for errors, I found my particular issue and it was related to another with Notifications ... I had removed "mimemail" from the system yet there were still some users that had notification settings to use mimemail. After fixing this, I no longer see any time limit problems. I'm assuming this is more than a coincidence ... essentially the time limit error report is bogus but there was an error to fix so you can't ignore the report.

 
 

Drupal is a registered trademark of Dries Buytaert.