I've been testing the Eloqua 6.x-1.0 on a Drupal 6.17 core. Webform 6.x-3.6 is installed.

With the Eloqua module disabled, cron runs successfully. Per Peter Lindstrom's suggestion (http://drupal.org/node/123269#comment-644012), I started capturing module info with Watchdog. With the Eloqua module enabled, Watchdog reports a "Cron run exceeded the time limit and was aborted." warning as the next event after running Eloqua cron. I even tried version 1.2 of eloqua.cron.inc. from CVS.

Any ideas?!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

CKoch’s picture

The first question I would have to ask is whether you have curl installed. If it were not installed, the call to curl_init would through a fatal php error, which would in turn lead drupal to believe that "Cron run exceeded the time limit and was aborted" because the script stopped running in an abnormal manner.

CKoch’s picture

This patch will add a check to ensure that
1. Curl is installed.
2. That there isn't a runaway exception, which will cause cron to give that error if something happens to Curl.
3. To ensure that we don't attempt to use a NULL curl-resource handle

greg.harvey’s picture

Status: Active » Needs review
drupalninja99’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +RTBC

This looks good to me. I will want this ported to D7 as well.

drupalninja99’s picture

Attaching d7 patch

drupalninja99’s picture

Version: 6.x-1.0 » 7.x-1.0
drupalninja99’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -RTBC

Pushed to 6.x-1.x and 7.x-1.x

Status: Fixed » Closed (fixed)

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