Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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?!
Comment | File | Size | Author |
---|---|---|---|
#5 | cron_installed-1057842-d7-05.patch | 5.08 KB | drupalninja99 |
#2 | cron_installed-1057842-02.patch | 2.87 KB | CKoch |
Comments
Comment #1
CKoch CreditAttribution: CKoch commentedThe 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.
Comment #2
CKoch CreditAttribution: CKoch commentedThis 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
Comment #3
greg.harveyComment #4
drupalninja99 CreditAttribution: drupalninja99 commentedThis looks good to me. I will want this ported to D7 as well.
Comment #5
drupalninja99 CreditAttribution: drupalninja99 commentedAttaching d7 patch
Comment #6
drupalninja99 CreditAttribution: drupalninja99 commentedComment #7
drupalninja99 CreditAttribution: drupalninja99 commentedPushed to 6.x-1.x and 7.x-1.x