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

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

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).

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.

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.

Nope, cron semaphore is numeric (time).

You guys using poormanscron?

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.

subscribing

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.

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?

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.