Flaming red errors upon bulk processing

webchick - April 10, 2009 - 02:28
Project:Calais
Version:6.x-3.1
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed
Description

There are a couple of stray dpm()s in calais_batch_process(). D'oh. :(

#1

febbraro - April 10, 2009 - 03:18

At least you got the ones without profanity :)

Was this killing your bulk process? Here is a patch if it did.

Fixed in CVS

AttachmentSize
calais-batch-dpm.patch 1.01 KB

#2

webchick - April 10, 2009 - 03:41
Status:active» fixed

Haha. ;)

I just enabled Devel module, but figured this might trip someone else up. Thanks for the fix!

#3

System Message - April 24, 2009 - 03:50
Status:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.

#4

DavidWhite - June 24, 2009 - 13:52
Status:closed» active

I applied the patch, and now when I go to do bulk processing, I don't get the fatal error, but I DO get the "An error occurred" message on the bulk processing page, when I'm such-and-such a percentage done.

Here's an example:

Calais Bulk Processing has encountered an error.
Please continue to the error page

An error occurred. /batch?id=52&op=do

We checked our error logs through Watchdog and some of our other log files and couldn't find anything. Apache is reporting this process as a POST, so I increased the max_input_time in our WHM from 1 minute to 2 minutes. Looks like we are still getting this "error" that isn't reporting any logs.

Edit: After reviewing the logs on this batch attempt (id=52) at this, I just found that dblog reported a 500 - Internal Server Error:

Message: Calais processing error: (500 - Internal Server Error)

Any ideas?

#5

febbraro - June 24, 2009 - 16:05
Status:active» closed

Please open a new issue for this and don't open a previously closed one as your problem is different.

However the error you are seeing is actually an error from the Calais service itself and not from this module, it is just reporting the error returned. Could be a problem on their part. Try again and see if you still get the same problems? Dont forget to open a new issue too :)

#6

reikiman - July 11, 2009 - 23:23

I just want to point out this was fixed 3 months ago "in CVS" but the current release still has this error in it.

#7

febbraro - July 27, 2009 - 03:12

Thanks, I had forgotten. 3.2 is now released.

 
 

Drupal is a registered trademark of Dries Buytaert.